[Pharo-project] Trait bug to fix....
alexandre at bergel.eu
Wed Jan 21 16:55:25 EST 2009
Maybe the solution is to not have this methods. Required methods are
easily inferred. There is no need to ask the user to define methods...
On 21 Jan 2009, at 22:03, 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.
> 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:
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
Alexandre Bergel http://www.bergel.eu
More information about the Pharo-dev