"Fare" == Far <Far> writes:
Fare> Oh, I used uiop:dump-image, which apparently always uses :executable t. Fare> Maybe it's a mistake, but that's what released in 3.0.2. >> >> Can't say if that is a mistake or not, but that certainly explains it. >> I actually would prefer, though, that :executable were not the >> default, for exactly the issue you ran in to >> Fare> In this case, either dump-image should accept separate :executable and Fare> :standalone arguments, and/or use :executable executable on CMUCL, and Fare> :init-function restore-image Fare> only when standalone. Backward compatibility is a bitch, whereby Fare> :executable should default to T where practical, and :standalone Fare> default to executable where executable-p. Ugh. I hate backward
As it stands now, it seems that with cmucl only executable images can be created. That seems not right.
I'm willing to break backward compatibility for asdf and cmucl, in this one case. :-) I doubt many people use executable images; I rarely do and when I do it's mostly for testing.
Ray