[closer-devel] ContextL: allow other keys in (re)initialize-instance methods for metaclasses

[Pascal Costanza]

Hi Paul,

I'm hesitating to make such a change, because it would weaken checking initialization arguments for validity.

Under normal circumstances, it is possible to make more initialization arguments valid for subclasses. See Section 7.1.2 of the HyperSpec. This also applies to metaobject classes. If for some reason this doesn't work for you, I would like to know about it and see whether something needs to be fixed. Please send some example, and some information which CL implementation you are using to test this.

Pascal

P.S.: I'm curious to hear about what you use ContextL for, and what you are adding in your subclasses. If you prefer, please feel free to contact me by private email on this. Thanks.

On 14 Mar 2012, at 21:56, Paul Sexton wrote:

> Hi
> 
> At present the metaclasses in contextl choke during initialisation if
> they are passed keys that they do not recognise. This makes it very
> difficult to create metaclasses derived from those classes, if the
> derived metaclasses need to be passed their own arguments a la
> ':in-layer'.
> 
> Including &allow-other-keys in the argument lists for
> (re)initialize-instance in cx-classes-in-layer.lisp and
> cx-layer-metaclasses.lisp seems to fix this, and doesn't seem to have
> any downsides. Would you consider making this change?
> 
> Thanks
> Paul
> 
> _______________________________________________
> closer-devel mailing list
> closer-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/closer-devel

--
Pascal Costanza