abcl mit Homebrew, apk, apt, MacPorts, Nix installieren

Projektlinks

• Homepage

Befehle und Aliase

• abcl

Projektgeschichte

The official homepage says ABCL was originally started as a scripting language for the J editor. It later grew into a standalone Common Lisp implementation on the JVM, with support for JSR-223 so it can act as a Java scripting engine and with Java-to-Lisp integration APIs for embedding Lisp in Java applications.

Adoptionsgeschichte

ABCL occupies a particular niche among Common Lisp implementations: it lets Lisp code run where a JVM is already the deployment target. The supplied package-manager metadata lists it in APK, Homebrew, Debian, MacPorts, Nix, and Ubuntu, reflecting its role as both a language runtime and a Java ecosystem bridge.

Wie es verwendet wird

Official documentation shows ABCL being run as a jar with java -jar abcl.jar, used as an interactive REPL, embedded from Java, and connected to Common Lisp tooling such as ASDF, Quicklisp, and SLIME.

Warum Paket-Nerds sich dafür interessieren

Package maintainers care about ABCL because it is a Common Lisp runtime whose runtime contract is Java rather than a native Lisp image. That makes Java version support, jar layout, wrappers, ASDF integration, and contrib artifacts central packaging concerns.

Zeitleiste

• 2016: Official GitHub mirror/repository metadata shows the armedbear/abcl repository created.
• 2026: Official ABCL release archive lists 1.10.0 artifacts, including abcl.jar and abcl.pdf.

Related projects

• ABCL is tied historically to the J editor and operationally to the JVM, Java scripting APIs, ASDF, Quicklisp, and SLIME.

Quellen

• Official homepage, FAQ repository section, README, releases index, GitHub repository metadata, and source_facts.package-manager.