[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


The dialect of Common Lisp which Paul Robertson (my boss) wrote for the 386,
and which later became the basis for the Cloe Runtime system (our native 386 Lisp)
is an example of a Lisp where the implementor assumed that EXPORT was to do
an implicit import. As Paul explains it to me, he doesn't see any ambiguity.
The documentation says it makes the argument symbols accessible as externals
of the designated package, and the only way to do that is to first import them
if necessary, so that's what he does. He's not even sure why it needs a
clarification -- from his point of view, all other implementations are simply
buggy. I have to say I think he makes perfectly believable case and it's
arguably reasonable to call this a request for an incompatible change, not just
a clarification. But in any case, I think there's no question that there's at
least an ambiguity.  (By the way, Paul's preference is for EXPORT-IMPORT:YES,
but I'm pretty sure he can be talked into EXPORT-IMPORT:NO if that's what everyone
seems to think is best.)

The reason for this issue in the first place is that we have an outstanding
bug report from a Cloe customer who says that EXPORT is not doing an implicit
IMPORT on the 3600 (while it is doing the IMPORT on the 386) and I'm trying
to figure out which side to fix. So this is not a contrived issue (as Jonl
suggested it might be).