Re: [clisp-list] Re: standalone executables & command line arguments

[Pascal B. <pj...@in...>]

Sam Steingold writes:
> > * Klaus Weidner <xj@j-z-c.pbz> [2006-01-26 11:43:47 -0600]:
> >
> > :argument-handler :standalone
> >
> > 	All arguments, including flags starting with '-', are placed into
> > 	the EXT:*ARGS* variable. This allows standalone executables to
> > 	fully handle all argument processing. The application is
> > 	responsible for handling any flag arguments normally handled
> > 	by the CLISP runtime if that functionality is required.
> 
> this will disable -M and -x.
> I understand that someone might want to re-implement "ls" with clisp and
> this will prevent him.
> 
> Nevertheless, I believe it is important that someone who receives a
> clisp-based application can get a clisp repl by merely typing
> $ app -x '(saveinitmem)'
> $ app -M lispinit.mem
> or just
> $ app -x '(saveinitmem "clisp" :executable t)'
> $ ./clisp

Couldn't this be archived with an environment variable?

$ app -x
I am app and I print 'X'.
$ CLISP_ARGUMENTS="-x '(progn (princ (lisp-implementation-version)) (ext:quit 0))'" app -x
2.38 (2006-01-24) (built 3347193361) (memory 3347193797)
$ CLISP_ARGUMENTS="-x ' (princ (lisp-implementation-version))'" app -x
2.38 (2006-01-24) (built 3347193361) (memory 3347193797)
I am app and I print 'X'.
$ 

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

What is this talk of 'release'? Klingons do not make software 'releases'.
Our software 'escapes' leaving a bloody trail of designers and quality
assurance people in it's wake.