>>> I was playing with compiledMethod and MethodReference and it would be
>>> great if they could be more
>>> polymorphic:
>>>
>>> MethodReference>>methodClass
>>> ^ self actualClass
>>
>> It will probably not do any harm, but why should a MethodReference be
>> polymorphic with a compiled method?
>
>
> like that we have a better system with less iskindof and methodClass
> vs. actualClass
> a MethodReference is a kind of wrapper for compiled method at the
> level of the tools
> so we would all gain having a good intersection between the two.
yes, absolutely, good idea.
Also useful:
MethodReference>>selector
^self methodSymbol
> >> I was also thinking that it would be nice to have the package
> >> associated with the MethodReference
> >> eg:
> >>
> >> (Character>>#escapeEntities) package
> >>
> >> -> PackageInfo-Base
> >>
> >> What do you think about that?
yes, makes sense.
But this would be CompiledMethod here, not MethodReference, IMO?
David
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
