[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
When is a package name equivalent to a package?
- To: "David A. Moon" <moon%scrc@MIT-MC.ARPA>
- Subject: When is a package name equivalent to a package?
- From: "Scott E. Fahlman" <Fahlman@CMU-CS-C.ARPA>
- Date: Thu, 25 Apr 1985 02:04:00 -0000
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: Msg of 24 Apr 1985 20:50-EST from David A. Moon <Moon at STONY-BROOK.SCRC.Symbolics.COM>
- Sender: FAHLMAN@CMU-CS-C.ARPA
I think the manual is quite clear.
p.183 requires that the value of *package* be a package.
p.182 specifies that certain functions, including INTERN, shall accept strings
and symbols in place of packages. As is unfortunately typical of the CLM,
this specification is not repeated in the documentation of each of the affected
functions, so it's quite easy to overlook.
Are we looking at the same page 182? Where does it say that? In the
last paragraph it says that "Any argument described as a PACKAGE NAME
may be either a string or a symbol." Is that waht you're thinking of?
Intern takes a package argument, but says nothing about taking a package