Subject: Re: temporarily setting a package From: Erik Naggum <email@example.com> Date: 1998/04/14 Newsgroups: comp.lang.lisp Message-ID: <firstname.lastname@example.org> * Sam Steingold | I am highly reluctant to have yet another file. I have a special file | with a bunch of system-specific stuff, like your reduce code, | *gc-verbose* for CMUCL, *warn-on-floating-point-contagion* for CLISP etc. | So, I guess, I should have asked about how to have your code in a file | with a lot of other junk. Obviously, I can put it as the very last | statement (right?), but I don't like it. I fail to understand the charm of loading a file that could place symbols and function definition into whatever package happens to be the value of *PACKAGE* at the time of loading. why not always use IN-PACKAGE to make sure you get all the stuff int the right packages? IN-PACKAGE can be repeated in a file, since it affects the reader's behavior after it has been evaluated. #:Erik -- religious cult update in light of new scientific discoveries: "when we cannot go to the comet, the comet must come to us."