[Openmcl-devel] [Re: MOP Question: structure of Lambda list for direct-slot-definition-class]

rm at fabula.de rm at fabula.de
Mon Feb 28 15:49:47 UTC 2005


On Tue, Feb 22, 2005 at 05:51:13PM -0700, Gary Byers wrote:
> [... snip ...]
> I'm not convinced that it provides the best way of handling that
> problem, but Figure 5.2 convinces me that that's what the paragraph
> quoted above is trying to say (e.g., that non-standard slot options
> should not be treated consistently and resolving ambiguity - if
> that's possible - should be left up to code that actually handles
> the initargs.)
> 
> So yes (kicking and screaming), this should be changed (as should
> any code like the SHARED-INITIALIZE method above) that depends on
> current behavior.

Hello Gary,

will this be changed in the upcomming release? I just recompiled bleeding-
edge-cvs and my original code still breaks. Where actually is that part of
the MOP implemented in the source files? I couldn't find the place where
the slot definition initargs are "canonisized" (i.e. the wrapping into lists
happens).

 Thanks RalfD



More information about the Openmcl-devel mailing list