| Notes on CL: - why nothing on the "compiler" line? Everytime you load a snippet or a file with SBCL, it compiles it (to machine code). There's also compile-file. - interpreter: likewise, all code is compiled by default with SBCL, not interpreted, even in the REPL. To use the interpreter, we must do this: https://github.com/lisp-tips/lisp-tips/issues/52 - command line program: the racket cell shows the use of -e (eval), the same can be done with any CL implementation. - since the string split line introduces cl-ppcre, one could mention cl-str :D (plug) (much terser join, trim, concat etc) - ah ok, for dates and times, flattening a list, hash-table literals… we need more libraries. - more files operations: https://lispcookbook.github.io/cl-cookbook/files.html - emacs buffers: now compare with Lem buffers 8-) - posix-getenv: I'd rather use uiop:getenv (comes in implementations). - uiop:*command-line-arguments* - exit: uiop:quit - uiop:run-program (sync) / launch-program (async) - java interop: with LispWorks or ABCL (or other libraries) my 2c |
(1) https://news.ycombinator.com/item?id=47779659