(roll m3tti)Cool new lib for #abcl to integrate java interop more deeply.
simendsjoTested with #SBCL, #ECL, #CCL and #ABCL.
Calling just `version` use the following defaults:
```
(version :version '(or version-file-line-0 system-version)
:pre-release '(or version-file-line-1 (when git-non-main-branch (and git-current-branch git-current-commit)))
:build-metadata '(git-current-branch git-current-commit current-time))
```
It tries to locate your system based on the package you're in, but you can specify directly by passing a `:root` argument.
svetlyak40wtI just found a very interesting #CommonLisp project which shows how to extend the LOOP macro: https://github.com/Gleefre/loop-continue
It was added to Ultralisp.org recently.
This code should work on #SBCL, #CLASP, #ALLEGRO, #ABCL and #ECL implementations.
LisPi@Elizafox Alternatively, one can use #ABCL for #CommonLisp or #Kawa for #Scheme when performance is critical (at the cost of CL's niceties).
vintage screwlisp account@scdollins Java #Processing works well inside #abcl #CommonLisp if you're into that. Cool generative art.
@maegul Interop being desirable wouldn't be much of a good reason, there's #ABCL and several other FFI libraries for JVM interaction.
An abstraction library dynamically papering over the differences based on what's available at runtime would've been perfectly feasible.
I honestly think the main reason was NIH.
@natty That list comprises a large part of why I dislike #Java as a language.
Basically all of those features can be trivially added in #JVM #Lisp languages like #KawaScheme and #ABCL.
Having to wait years for the devs to do something useful and so basic is just silly.
@starshine
Pretty much always did. And even for #CSP (the main #Golang attraction), there were a few libraries in Java proper for it too (nevermind #Clojure).