ccl
sbcl
Our great sponsors
ccl | sbcl | |
---|---|---|
18 | 59 | |
801 | 1,764 | |
1.6% | 1.2% | |
7.3 | 9.9 | |
5 days ago | 5 days ago | |
Common Lisp | Common Lisp | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ccl
-
The IDEs we had 30 years ago and we lost
The descendant of CCL runs on modern Intel Macs. (It also runs on Linux and Windows but without the IDE.) The modern IDE is quite a bit different from the original. In particular, it no longer has the interface builder. But it's still pretty good. It is now called Clozure Common Lisp (so the acronym is still CCL) and you can find it here:
If you want to run the original that is a bit of a challenge, but still possible. The original was never ported directly to OS X so you have to run it either on old hardware or an emulator running some version of the original MacOS, or on an older Mac running Rosetta 1. In the latter case you will want to look for something called RMCL. Also be aware that Coral Common Lisp was renamed Macintosh Common Lisp (i.e. MCL) before it became Clozure Common Lisp (CCL again).
This looks like it might be a promising place to start:
If you need more help try this mailing list:
- The Saga of the Closure Compiler, and Why TypeScript Won
-
plain-common-lisp: a lightweight framework created to make it easier for software developers to develop and distribute Common Lisp applications on Microsoft Windows
I was not aware that UIOP provided that function. plain-common-lisp used to be implemented with Clozure CL but eventually moved to SBCL due to the lack of maintenance of CCL. But now there is a hard dependency on SBCL.
-
Consuming HTTP endpoint using Common Lisp
I have decided it is time to have some fun and use Common Lisp to create algorithm representation that deals with parallel execution. For this I decided to use Clozure common lisp, put basic Qucklisp there and load some libraries to do this.
- Corman Lisp development environment for MS Windows
-
Common Lisp for microservices
The only thing I've not seen said yet is that Clozure Common Lisp will probably be smaller at runtime than the more common SBCL. The latter has better support, however.
-
Profiling CCL on OS X -- options?
Currently https://ccl.clozure.com isn't responding...
-
is CLISP still recommended to use ?
Clozure Common Lisp also runs on Windows and is more widely used and more recently updated: https://github.com/Clozure/ccl/releases
- Common Lisp Windows 10 install
-
Tell HN: My experience with Common Lisp as beginner
git clone https://github.com/Clozure/ccl.git ccl-dev
sbcl
-
Arena Allocation in SBCL
Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.
That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.
https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...
- Implementing Interactive Languages
-
Garbage Collection in a Large Lisp System (1984) [pdf]
related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
https://applied-langua.ge/~hayley/swcl-gc.pdf
build with
./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).
-
SBCL: merge of mark-region GC
The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.
- Owner of Symbolics Lisp machines IP is interested in a non-commercial release
- Steel Bank Common Lisp
-
Wasix, the Superset of WASI Supporting Threads, Processes and Sockets
>Just like your usual hardware CPU cannot run Common Lisp directly, neither can WASM.
My usual hardware CPU runs Common Lisp code beautifully, thanks to this native x86-64 compiler: https://www.sbcl.org/
-
Common Lisp – Myths and Legends
You can get SBCL for free which actually beats Lispworks on performance AFAIK: https://www.sbcl.org/
-
Turning Linux Into a Usable Lispy Machine?
sbcl w/ linedit for repl/shell
What are some alternatives?
abcl - Armed Bear Common Lisp <git+https://github.com/armedbear/abcl/> <--> <svn+https://abcl.org/svn> Bridge
sb-simd - A convenient SIMD interface for SBCL.
BQN - An APL-like programming language. Self-hosted!
cl-ppcre - Common Lisp regular expression library
maiko - Medley Interlisp virtual machine
seed7 - Source code of Seed7
common-lisp-jupyter - A Common Lisp kernel for Jupyter along with a library for building Jupyter kernels.
lisp-xl - Common Lisp Microsoft XLSX (Microsoft Excel) loader for arbitrarily-sized / big-size files
cloc - cloc counts blank lines, comment lines, and physical lines of source code in many programming languages.
portacle - A portable common lisp development environment
sbcl-problem-on-AppleM1 - Problem on SBCL/M1 Mac
qlot - A project-local library installer for Common Lisp