id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
605	Saving runtime options in CCL:SAVE-APPLICATION	Adlai	gb	"SBCL has an option when you dump an executable image to have the new image start up with the same amount of reserved heap space, stack space, etc, as the current image. Also, using this option means that the all command-line arguments are passed directly to the executable image.

Currently, the CCL kernel handles some command-line arguments unconditionally, which is a nuisance for producing completely stand-alone applications. Having this option would both enable complete control of command-line argument handling, and would let a saved application start up with a specified amount of heap space, stack space, etc, rather than the defaults.

Example:

; Currently
(ccl:save-application ""frob-text""
                      :prepend-kernel t
                      :toplevel-function #'main)
...
$ ./frob-text document.txt
Couldn't load lisp heap image from document.txt

; Ideally
(ccl:save-application ""frob-text""
                      :prepend-kernel t
                      :toplevel-function #'main
                      :save-runtime-options t)
...
$ ./frob-text document.txt
<frobs document.txt>"	defect	closed	normal		project hosting	unspecific	wontfix	application command-line kernel