[Pharo-project] Trait bug to fix....

Stéphane Ducasse stephane.ducasse at inria.fr
Wed Jan 21 16:53:08 EST 2009


I'm confused I do not undersatnd why if B is a subclass of A it uses T  
too.
I have to check the bugs tracker

On Jan 21, 2009, at 10:03 PM, Adrian Lienhard wrote:

> Any suggestion for how to implement this? Without using some
> reflection tricks, this would imply that the marker methods have to be
> added and removed depending on the methods added and removed in
> superclasses. This would significantly complicate the implementation.
>
> BTW, this only is an issue if m is implemented as "self
> explicitRequirement". I never really understood why one would want to
> explicitly declare requirements. In the end, the difference is to get
> a different exception than a MNU. If one wants this to see what
> methods still need to be implemented in a class I would rather suggest
> to extend the tools to show this (even the ones not explicitly
> declared) and not use explicit declarations. The algorithm by
> Nathanael to do exactly this is already in the image.
>
> Adrian
>
> On Jan 21, 2009, at 21:37 , Stéphane Ducasse wrote:
>
>>> T requires m
>>>
>>> A uses: T
>>>     m ^#fromA
>>> B subclass: A uses: T
>>>
>>> M new m => error explicit requirement
>>
>> Begin forwarded message:
>>
>>> http://bugs.squeak.org/view.php?id=6534
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>





More information about the Pharo-dev mailing list