Re: COMPILE-FILE-SYMBOL-HANDLING:HOME-PACKAGE

[sandra%defun@cs.utah.edu (Sandra J Loosemore)]

What you describe is not what proposal HOME-PACKAGE was intended to
say.  It is, however, a behavior that I would consider reasonable.  It
has the benefit of offering somewhat tighter error checking, but the
disadvantage that it is even less forgiving of minor changes to the
package structure than proposal HOME-PACKAGE.  For example, suppose
you compile your file in package P1 that uses the P2 package, and you
reference a symbol FOO whose home package is P1.  If, between compile
and load time, another symbol called FOO is exported from the P2
package, you lose.

If there is a strong belief that this behavior is correct, I don't
have any objection to adding it as another proposal and/or modifying
proposal REQUIRE-CONSISTENCY to allow this as a legitimate
implementation technique, other than that it's a lot of work. :-)

-Sandra
-------