> It's implementation dependent so you have to know your compiler well. In any larger application you have to know your compiler and the special libraries well

> It's implementation dependent so you have to know your compiler well. In any larger application you have to know your compiler and the special libraries well. GCC, CLANG, whatever... SBCL is kind of large. Other open source Common Lisps create smaller applications: CLisp, CCL, ECL, ... Some thought there was a use for delivery Common Lisp with or without GC. But it has not caught on widely. See for example Thinlisp, CLICC, mocl (derived from CLICC) and others. Those have compilers written in Common Lisp, which translated the code to static C. In case of Thinlisp without GC - its origin is in soft-realtime expert systems for process control. Thinlisp is probably not much used, but a related compiler (not publicly available) is still used for product development. There were and still are inhouse delivery compilers. Also specialized languages: You develop in a Common Lisp environment, but write in a special language. SubL, Stella, ... For example Cyc is written on top of SubL, which is derived from Common Lisp (and can be used inside Common Lisp) and the Cyc application then can run on top of C or Java.