3 ms·
As someone else noted, SBCL's `SB-EXT:SAVE-LISP-AND-DIE` ends up producing hilariously large executables. The solution I've settled on for bags of small, sharp
by kmstout 3y ago
As someone else noted, SBCL's `SB-EXT:SAVE-LISP-AND-DIE` ends up producing hilariously large executables. The solution I've settled on for bags of small, sharp tools is to simply have an omnibus program that includes a variety of functionality as subcommands, and that can dispatch to the appropriate function based on the name it was run as (i.e., the value of argv[0]). One of those commands will pepper a directory of your choice with soft links to the omnibus program, each named for a subcommand.
- kagevf 3y agoRecently, I read about someone who basically had a single running image and it would dispatch to the right function based on the command names sent to it, and the image was running swank, which sounded like a neat idea. I saw it in a comment, either here or on reddit ...