3 ms·
> I suppose you use it for servers and you don't deploy SBCL to end-user machines? AFAIK, most Common Lisp applications are deployed in a single binary, bundle
by pcr910303 7y ago
> I suppose you use it for servers and you don't deploy SBCL to end-user machines?
AFAIK, most Common Lisp applications are deployed in a single binary, bundled with the lisp implementation. SBCL isn’t an exception, so if someone would deploy an SBCL app to end-users, one would build a self-contained application with the `sb-ext:save-lisp-and-die` function [0].
[0]: https://lispcookbook.github.io/cl-cookbook/scripting.html https://lispcookbook.github.io/cl-cookbook/scripting.html
- codr7 7y agoThis feature is a godsend when implementing your own language [0] on top since everything is wired up automatically when the application starts. Compared to emitting C or whatever where you need to include code to stitch the runtime state together. Makes compiling standalone executables so easy [1] it feels like cheating. [0] https://github.com/codr7/lila https://github.com/codr7/lila [1] https://github.com/codr7/lila/blob/master/main.lisp https://github.com/codr7/lila/blob/master/main.lisp
- cheez 7y agoI never managed to get SLAD to work with Qt bindings and stuff. CL was my preference many years back, but practical usage at the fringes required me to be a SBCL expert. Sadly, I am/was not :-( so now I am a Python Pleb.