From: Klaus Ebbe Grue <grue@di...> - 2006-07-18 13:11:35
> Subject: [clisp-announce] GNU CLISP 2.39 (2006-07-16)
> SAVEINITMEM now accepts :SCRIPT argument that disables interpreting
> the first positional argument as the script name; and :DOCUMENTATION
> argument that is printed by the new -help-image command line option.
> See <http://clisp.cons.org/impnotes/image.html> and
> <http://clisp.cons.org/impnotes/clisp.html#opt-help-image> for details.
I have moved to clisp-2.39 with absolutely no problems. And :SCRIPT is a
very great enhancement.
But it seems that
needs a little more info.
If I do a saveinitmem with :executable t and a non-nil init-function then
prompt> mymemorydump abc
passes abc to the init-function in *args* as it should. But if I do
prompt> mymemorydump -abc
then I get
GNU CLISP: invalid argument: '-abc'
GNU CLISP: use '-h' for help
It seems that if the *first* argument of the executable memory dump
consists of a hyphen followed by at least one more character, then it is
taken to be a clisp argument. And it is considered a fatal error if that
argument is unknown to clisp.
The GNU CLISP: invalid argument: '-abc' message is generated even before
CUSTOM:*INIT-HOOKS* is processed.
This suggests that
should say that some processing of the command line arguments occurs
before step 1.i: Run all functions in CUSTOM:*INIT-HOOKS*
By the way: is there a way to disable the "GNU CLISP: invalid argument:"
From: Klaus Ebbe Grue <grue@di...> - 2006-07-21 13:13:32
On Thu, 20 Jul 2006, Sam Steingold wrote:
>> But it seems that
>> needs a little more info.
>> By the way: is there a way to disable the "GNU CLISP: invalid
>> argument:" fatal error?
Then I will use the work-around to let all options to my executable clisp
memory dumps start with a colon instead of a hyphen (so e.g.
'myprogram -h' gives help on clisp and 'myprogram :h' gives help on
If you ever find time to look at :script again, I hope you will consider a
solution which disables argument-processing completely for executable
memory dumps with :script=nil as in the patch I submitted, possibly with
a twist such that e.g. argv="-clisp" overrides :script=nil and
Anyway, executable memory dumps and the :script keyword will make my
clisp-programs much more user friendly, so thanks again.