From: Sam S. <sd...@gn...> - 2005-11-01 14:31:27
|
> * Juan C.Acosta Guadarrama <thn...@va...-pynhfguny.qr> [2005-11-01 15:05:32 +0100]: > > On 31 Oct 2005, at 20:00, Sam Steingold wrote: > >>> * Juan C.Acosta Guadarrama <thn...@va...-pynhfguny.qr> >>> [2005-10-31 19:19:20 +0100]: >>> >>> according to the man pages, I may realise it by using switch >>> -c. >> >> where does the man page say that? > > well, it reads: > >>>> -c lispfile ... >>>> Compiles the specified lispfiles to bytecode (*.fas). >>>> The com- >>>> piled files can then be loaded instead of the >>>> sources to gain >>>> efficiency. yes, so "clisp -c lispfile" will compile the "lispfile". > then, after some other lines it reads: > >>>> lispfile [argument ...] >>>> Loads and executes a lispfile. There will be no >>>> read-eval-print >>>> loop. Before lispfile is loaded, the variable *args* >>>> will be >>>> bound to a list of strings, representing the >>>> arguments. The >>>> first line of lispfile may start with #!, thus >>>> permitting clisp >>>> to be used as a script interpreter. If lispfile is -, >>>> the stan- >>>> dard input is used instead of a file. If lispfile is >>>> the empty >>>> string or -- the rest of the arguments is still >>>> available in >>>> *args* , for parsing by the init-function of the >>>> current image. >>>> This option must be the last one. No RC file will be >>>> executed. yes, "clisp lispfile" will load and execute "lispfile". where does it say that "clisp -c lispfile" will load and execute anything? > http://www2.in.tu-clausthal.de/~guadarrama/updates/clisp.html please also link to <http://clisp.cons.org/impnotes/>. <http://clisp.cons.org/clisp.html> is just an "invocation manual". -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.jihadwatch.org/> <http://ffii.org/> <http://www.savegushkatif.org> <http://www.mideasttruth.com/> <http://www.iris.org.il> main(a){a="main(a){a=%c%s%c;printf(a,34,a,34);}";printf(a,34,a,34);} |