> On 16 Sep 2016, at 14:55, Faré <fah...@gmail.com> wrote: > > ASDF distinguishes image-op from program-op. The former is supposed to > create an image from which you can resume development. The latter is > supposed to create a self-contained executable application that can > hopefully be delivered with minimal additional support files > (depending on the implementation). Both invoke dump-image (or > create-image, on ECL & co), but with slightly different options. > > I admit that CMUCL has fallen completely out of my cache, because it > requires a 32-bit compiler for dumping executables, and recent Linux > distributions don't bother with that anymore. I remember it had > command-line issues, but I thought they were resolved, and you could > *somehow* access unprocessed arguments if you used > :process-command-line nil. If not, I'd say that's a bug to be resolved > with the CMUCL maintainer, if still active.
I’ve talked to Raymond Toy about this approximately a week ago here: https://gitlab.common-lisp.net/cmucl/cmucl/issues/29 and he convinced me that what CMU CL does is not a bug. Elias
