[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: in-package problems
- To: info-mcl
- Subject: Re: in-package problems
- From: tar@ISI.EDU (Thomas A. Russ)
- Date: 8 Jan 92 17:15:05 GMT
- In-reply-to: firstname.lastname@example.org's message of 7 Jan 92 16:44:52 GMT
- Newsgroups: comp.lang.lisp.mcl
- Organization: USC-ISI
- References: <1992Jan7.email@example.com>
- Reply-to: firstname.lastname@example.org
- Sender: email@example.com
In article <1992Jan7.firstname.lastname@example.org> email@example.com writes:
I am having some problems with the IN-PACKAGE
macro in MCL2.0b1. IN the old version (Mac. Allegro
1.3.2) is is simple to use IN-PACKAGE with a variable
name, however this appears no longer to be possible.
Am I doing something silly, if not how can I get around
this problem and pass package names as variable?
Thanks for any help
There was an incompatible change in in-package in the CL standard.
The X3J13 committee voted in March 1989 to change the functionality of
in-package and to make it a macro. The new definition specifies that
the argument to in-package is NOT EVALUATED. (See Steele, CLtL 2nd
Ed., p. 263-264)
You cannot do what you want using in-package. The closest you can get
would be to BIND the variable *package* to the value of a package
created earlier, but I think this would be a bad idea. Why do you
want the name to be in a variable anyway?