> I agree with this. The existing "--script" can be renamed "--load" > because that's what it does: it loads the file into the interaction > environment. I don't understand what "loads the file into the interaction environment" means. What kind of files are allowed? I am guessing the file should look like a script file? Must it start with an import?
On Mon, Jun 1, 2009 at 6:38 PM, Abdulaziz Ghuloum <[email protected]> wrote: > > On Jun 1, 2009, at 11:03 AM, Derick Eddington wrote: > >> 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. > > I agree with this. The existing "--script" can be renamed "--load" > because that's what it does: it loads the file into the interaction > environment. > >> Ideas: >> >> Keep --r6rs-script. Remove --script. Remove --r6rs-repl. Add --repl. > > I'd rename --script to --load. > >> "ikarus --repl --r6rs-script" starts a REPL in an interaction >> environment of the script's top-level after running the script. > > Fine. > >> ikarus = ikarus --repl --r6rs-script import-ikarus--print-greeting.sps > > Fine. (not that there will be a separate file named such) > >> "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. > > I disagree here. I don't think "loading" should be the default > behavior (I don't like it much myself). How would you change the > options if we want an explicit "--load"? > (I'm having a brain freeze at the moment, so, I can't think) > > Aziz,,, >
