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

[Sam S. <sd...@gn...>]

> * Steven E.Harris <fru@cnavk.pbz> [2006-01-26 13:55:13 -0800]:
>
> Sam Steingold <sd...@gn...> writes:
>
>> Nevertheless, I believe it is important that someone who receives a
>> clisp-based application can get a clisp repl by merely typing
>
> I would expect it to be the prerogative of the author to make the
> implementation decision to use CLISP or some other system, and that
> decision here is not meant to be the business of the end-user. Why
> must every application created with CLISP also /be/ CLISP?

because the what you are distributing (e.g., clisp executable image)
does include full clisp (compiler, debugger &c) and I see no reason to
prevent the user from easily accessing it.

if you want full control over your application's options, you can use a
script.


-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
http://www.camera.org http://www.dhimmi.com http://pmw.org.il
http://www.honestreporting.com http://www.openvotingconsortium.org
Democrats, get out of my wallet! Republicans, get out of my bedroom!