# HG changeset patch # User Steve Losh # Date 1535138823 0 # Node ID 06e892f638d8993dd22c3f5f57d3e9f9f62b2946 # Parent 7c80c8de0ea531726f75219bae84c9a371a1b72b Links diff -r 7c80c8de0ea5 -r 06e892f638d8 content/blog/2018/08/a-road-to-common-lisp.markdown --- a/content/blog/2018/08/a-road-to-common-lisp.markdown Mon Aug 20 14:16:52 2018 +0000 +++ b/content/blog/2018/08/a-road-to-common-lisp.markdown Fri Aug 24 19:27:03 2018 +0000 @@ -939,23 +939,25 @@ implementations today, but they aren't the only actively-developed ones out there. There's plenty of others you might want to explore: -* [ABCL][TODO] runs on the JVM. -* [ECL][TODO] can be embedded in a C program. -* [CLASP][TODO] is still under development, but is an implementation designed to - be easy to interface with C++. -* [Lispworks][TODO] and [AllegroCL][TODO] are commercial implementations with - a lot of extra features. - -TODO more? +* [ABCL][] runs on the JVM. +* [ECL][] can be embedded in a C program, and can translate Common Lisp code to C code. +* [CLASP][] is still under development, but is an implementation designed to be easy to interoperate with C++. +* [Lispworks][] and [Allegro CL][] are commercial implementations with a lot of extra features and support, but are not free. (I omitted CLISP because I'm sore about them choosing a name that confuses the heck out of new people. Hey, I warned you this post would contain Opinions™.) -I personally tend to use SBCL for my personal projects, but I also make sure the -units tests for all my libraries run in CCL, ABCL, and ECL. This keeps me +I personally tend to use SBCL for my own projects, but I make sure the units +tests for all my libraries run in SBCL, CCL, ABCL, and ECL. This keeps me honest and gives me a reasonable degree of confidence that I'm writing portable code. +[ABCL]: https://common-lisp.net/project/armedbear/ +[ECL]: https://common-lisp.net/project/ecl/main.html +[CLASP]: https://github.com/clasp-developers/clasp +[Lispworks]: http://www.lispworks.com/ +[Allegro]: https://franz.com/products/allegro-common-lisp/ + ## Modern Common Lisp Common Lisp is old and stable, but that doesn't mean it's stagnant. The