From: Bruno Haible <bruno@cl...> - 2006-06-14 15:48:50
Don Cohen wrote:
> Here's a long standing problem that I only now begin to think of as a
> clisp bug. Let's see what the rest of you think.
> Consider a batch file with a command like
> clisp -i start.lsp -p MYPKG
> The behavior I see suggests that this is interpreted as something like
> (progn (load "start.lsp")(in-package "MYPKG"))
> The problem is that if the load breaks and the user aborts then he
> doesn't end up in MYPKG.
clisp -i start.lisp -p MYPKG
is meant to enable you, as a programmer, to work in package MYPKG,
package defined in start.lisp, with the functions defined in start.lisp.
Not less, not more.
If loading start.lisp already breaks, it does not make sense to drop
the user into package MYPKG: The package might not yet exist, or it
might be empty or incomplete.
If you wish a different behaviour, you can achieve it through the -x