4 ms·
For Common Lisp, there's ABCL ( https://abcl.org https://abcl.org ) which is a CL on the JVM and, otherwise, LispWorks bundles a nice Java FFI. But, additional
by fiddlerwoaroof 7y ago
For Common Lisp, there's ABCL ( https://abcl.org https://abcl.org ) which is a CL on the JVM and, otherwise, LispWorks bundles a nice Java FFI.
But, additionally, CL makes binding to C libraries really easy via CFFI and things like cl-autowrap ( https://github.com/rpav/cl-autowrap https://github.com/rpav/cl-autowrap ) so, when there isn't a native lisp library, it's often easy enough to just use a C library in your program (or, I suppose, anything that can compile to something compatible with C like `extern C` in C++ and the equivalent constructs in Rust)
- slyrus 7y agoIt would be nice if ABCL's JDK 11 support were brought into the main repo. Speaking of which, it would be nice if the main repo moved away from SVN to, e.g., gitlab. And, while we're at it, the issue tracker could be brought into the new millennium.
- fiddlerwoaroof 7y agoYeah, I just noticed this: https://mailman.common-lisp.net/pipermail/armedbear-devel/2019-April/003973.html https://mailman.common-lisp.net/pipermail/armedbear-devel/20... so, perhaps it's coming soon?