[Openmcl-devel] simple newby defpackage question

Hamilton Link hamlink at comcast.net
Mon Nov 15 09:05:16 PST 2004

You can use stand-alone exportation to add new exports and the like in 
files that add bits, but package dependencies and nicknames should 
probably be relatively statically definable (and accrue monotonically 
unless you're ripping stuff out).

Packages, imho, are there to control some of the raging fury that is a 
rapid-prototyping language. If you don't know yet what depends on what 
module-wise, then you should expect your package definitions to be 
revisited from time to time.

Possibly you could post the problem (if there is one) that the 
inability to extend a package object dynamically is causing you?


On Nov 15, 2004, at 6:39 AM, Gary Byers wrote:

> On Sun, 14 Nov 2004, Kenneth Tilton wrote:
>> If my guess is right, the default behavior of openmcl defpackage is to
>> replace rather than incrementally extend a package definition. I saw
>> this on Lispworks as well. That implementation had a global
>> *handle-existing-defpackage* one could set to :modify.
>> Does openmcl have a way to treat a defpackage as extending an existing
>> package?
>> kenny
> No.
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list