[closer-devel] OpenMCL and funcallable-standard-object

[Pascal Costanza]

On 11 Nov 2007, at 20:17, Vyacheslav Akhmechet wrote:

> On 11/11/07, Pascal Costanza <pc at p-cos.net> wrote:
>> Yes, OpenMCL doesn't support the generic function invocation protocol
>> as specified in AMOP, so there is not much use to export that symbol.
> Right, but I'm not talking about GF invocation. I have code that makes
> instances of classes funcallable. Because ACL doesn't automatically
> use FUNCALLABLE-STANDARD-OBJECT for classes with metaclass
> FUNCALLABLE-STANDARD-CLASS I have code that looks like this:
>
> (defclass foo (c2mop:funcallable-standard-object)
> (...)
> (:metaclass c2mop:funcallable-standard-class))
>
> I can easily add #+allegro to the superclass, but OpenMCL does support
> support FUNCALLABLE-STANDARD-OBJECT, it's just that it's not exported
> by Closer.

OK, I'll make it available as soon as possible...

>> There was a suggestion how to make at least parts of the protocol
>> work. As soon as I find the time to look more into this, it may  
>> happen
>> that I add this in a later version of Closer to MOP. But don't hold
>> your breath...
> That was probably the code I posted which I wrote to make parts of
> Weblocks work.

Yes, very likely, now that you mention it... ;)


Pascal

-- 
Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net
Vrije Universiteit Brussel, Programming Technology Lab
Pleinlaan 2, B-1050 Brussel, Belgium