On Wed, Apr 6, 2011 at 12:12 PM, Daniel Weinreb wrote:
> Possible approaches:
>
> (1) Too bad; you really do have to load
> the Lisp files that created those internal
> symbols after defining package X and
> before defining package Y.
>
> (2) For Y to export symbols of X that
> X does not export,
On 4/6/2011 1:12 PM, Daniel Weinreb wrote:
> In large Lisp systems, it's easy to run into problems with
> the order in which files are loaded and compiled.
>
> One often-vexing issue is where to put package
> declarations. If a file names an exported symbol
> such as foo:bar, the package foo with
Daniel Weinreb writes:
> However, in a situation I'm working on now, that
> doesn't work, because package X has
> (:import-from :y :a1 :a2), and the symbols
> :a1 and :a2 are not exported from :y. That
> is, X is exporting internal symbols of Y.
> This fails, because the symbols :a1 and :a2
> do
In large Lisp systems, it's easy to run into problems with
the order in which files are loaded and compiled.
One often-vexing issue is where to put package
declarations. If a file names an exported symbol
such as foo:bar, the package foo with its
export list must have been loaded earlier.
In gen
