[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: labrea!KMP%STONY-BROOK.SCRC.Symbolics.COM@labrea.Stanford.EDU
- Subject: Issue: EXPORT-IMPORT
- From: Jon L White <edsel!jonl@labrea.Stanford.EDU>
- Date: Wed, 3 Feb 88 17:47:47 PST
- Cc: labrea!CL-Cleanup%SAIL@labrea.Stanford.EDU, labrea!common-lisp%sail@labrea.Stanford.EDU
- In-reply-to: Kent M Pitman's message of Wed, 3 Feb 88 11:34 EST <880203113410.5.KMP@RIO-DE-JANEIRO.SCRC.Symbolics.COM>
The reason why some users may be mislead about EXPORT is that they fail to
heed the directive on the second line of p186: "See section 11.4 for details".
The one paragraph description of EXPORT on p186 is grossly incomplete without
reference to that other section, which cleary states: (p177, last paragraph)
"The function EXPORT takes a symbol that is *accessible* in some specified
package ... If the symbols is not accessible at all in the specified
package, a correctable error is signalled that, upon continuing, asks the
user whether the symbol should be imported." [my emphasis].
Every implementation I'm familiar with seems to implement the above
semantics rigidly; no one quietly imports the symbol without first
signalling an error.
-- JonL --