On Sun, 2009-05-31 at 16:11 +0300, Abdulaziz Ghuloum wrote: > It just occurred to me that the name --r6rs-repl might confuse people, > making them think it's a repl that obeys the R6RS semantics, which it's > not.
Yeah, I think that name is too confusing. > Maybe we should split the options into two groups: > > --repl (default) > --no-repl > > --script <script-name> > --load-script <script-name> (existing --script option) > --no-script > > with > ikarus --r6rs-script <file> == ikarus --no-repl --script <file> > and > ikarus <file> == ikarus --repl --load-script <file> > > Actually, coming to think of it, I don't think the "load-script" is > that useful now that we have a repl-in-a-script mode. Maybe Ikarus > should by default run as: > > ikarus == ikarus --no-script > ikarus <file> <arg>* == ikarus --script <file> <arg>* > > The command-line options need serious reworking. Any suggestions > welcome. I like --r6rs-script because it distinguishes from a future --r7rs-script (or --future-whatever) which may have different semantics, and we'll want to be able to have both for a while (I suppose). The name "--script" is too ambiguous, and entering a REPL should be explicit, IMO. Ideas: Keep --r6rs-script. Remove --script. Remove --r6rs-repl. Add --repl. "ikarus --repl --r6rs-script" starts a REPL in an interaction environment of the script's top-level after running the script. ikarus = ikarus --repl --r6rs-script import-ikarus--print-greeting.sps "ikarus --repl <file>*" loads the files into an interaction environment of (import (ikarus)) and then starts a REPL in that environment. "ikarus --repl" can be used to start a REPL without printing the greeting. "ikarus <file>+" (no --repl) loads the files into an interaction environment of (import (ikarus)) and then exits. -- : Derick ----------------------------------------------------------------
