I guess, while I am at it, which #lisp #commonlisp should I settle on
#ClozureCL, #GnuCommonLisp #gcl, #Clisp, #SteelBankCommonLisp (#sbcl)
@Absinthe SBCL. It is actively developed (unlike clozurecl), with monthly releases. It compiles to native code (unlike CLISP), the compiler has many unique features. That said, many implementations have their uses but if you're asking, then the answer is clear.
I very rarely hear about GCL. Last time I saw it mentioned, was in a source code hunk meant to be read by GCL specificially, followed by a comment like “my, is GCL broken”.
I very rarely hear about GCL. Last time I saw it mentioned, was in a source code hunk meant to be read by GCL specificially, followed by a comment like “my, is GCL broken”.
@akater I got both CCL and sbcl running, and they both seem pretty much the same. Sbcl just released 2.2 but I don't know if it will matter much. Added stuff about blocks. I still like CLisp repl from the command line works nice without adding redline around it
@Absinthe Using a Lisp (any Lisp) without SLIME or something similar, like in a basic CLisp repl, is a fairly terrible experience. Emacs will watch your parens for you, complete symbols, jump to definitions in code and to entries in the spec. SLIME will let you inspect the state of your program (= the state of your Lisp process(es)).
Features of CLISP vs ClozureCL vs SBCL are likely not noticeable to a beginner.
Features of CLISP vs ClozureCL vs SBCL are likely not noticeable to a beginner.
