3 ms·
We are working on a product written in Scheme. It's mostly just me currently. Not (currently) using Racket, but a set of libraries[1] on Gambit-C, as well as an
by pflanze 8y ago
We are working on a product written in Scheme. It's mostly just me currently. Not (currently) using Racket, but a set of libraries[1] on Gambit-C, as well as an interpreter written in C++[2]. We might take someone on board a few months from now (London/UK).
[1] https://github.com/pflanze/chj-schemelib https://github.com/pflanze/chj-schemelib
[2] https://news.ycombinator.com/item?id=18045890 https://news.ycombinator.com/item?id=18045890
- spacesuitman2 8y agoWhat about Racket's ability for arbitrary languages via #lang, not just macros? Are there any plans for this? It's really nice to be able to do #lang c and just write C that is FFI'd into racket so you can avoid using an external toolchain to compile.
- pflanze 8y agoI don't really have a use for this. Gambit-C allows to include C files or also strings of C code from a Scheme module and builds it as one. I haven't used Racket's FFI though, perhaps the real benefit is from parsing the C code to auto-generate bindings? Generally I'd like to reduce the use of C code in case I want to re-target the code to run in a different, not C based, environment. chj-schemelib will need work for general consumption, let me know if you want to use it. (If you're talking about the interpreter in C++, it's the other way around, write FFI declarations within C++ to allow Scheme access to C++.)