On Thursday, August 14, 2003, at 07:52 PM, Tim Rowledge wrote:

> Stephane Ducasse <ducasse at iam.unibe.ch> wrote:
>
>> If you look carefully all those implementors are in different
>> hierarchies.
>> The idea was to avoid to have another method in Object
> Given the same implementation is used and the same intent is in mind,
> why one earth can we not just put it in Object? Any class that needs to
> override or extend can do so. Putting the method in separate 
> hierarchies
> means that any new hierarchy needs yet another copy to be added - if
> the implementor even knows about it.
>

This was my MISTAKE. I do not have the time to fix. Just the time not 
to get too flooded by email.

> Alternatively, get rid of the whole concept and go to either class-side
> messages on SystemNavigation or istance side messages on a singleton
> global SystemNavigator. The latter leaves open the possibility of 
> having
> further instances (or subclass instances) that can dealwith outside 
> code
> or images.

I will propose a fix as soon as I have the time i.e., not before 15 
september except if I'm fedup of boring stuff and want to have some fun.

Stef


>
> tim
> --
> Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
> AAAAAA - American Association Against Acronym Abuse Anonymous
>