🚀 go-pugleaf

Tristan Reeves <moonshine@apex.net.au> wrote:

: The best way for dealing with this that I have seen is in Delphi (object
: pascal), in which you can have "name-resolution" statements in your class
: declaration. So you can say Intf1.X()=MyClass.Interface1X(), and then calls
: to that interface method [X()]will get mapped to the specified method
: [Interface1X()].

That is also - more or less - what Eiffel does.

http://www.elj.com/eiffel/ij/inheritance/mi/ describes the problem
with C++:

''In C++, you must use the scope resolution operator in the code, every
  time you run into an ambiguity problem between two or more members. This
  clutters the code, and makes it less malleable, as if anything changes
  that affects the ambiguity, you potentially have to change the code
  everywhere, where the ambiguity occurs.''

 - http://www.elj.com/eiffel/ij/inheritance/mi/

Eiffel advocates renaming - through inheritance.  That way - if you get a
name clash - you don't have to go through all the existing code renaming
all the calls to the newly-ambiguous method - and you can still find the
names of the methods you are interested in the class where they are called.

Could Java be changed to do things that way?  I don't see why not.
-- 
__________
 |im |yler  http://timtyler.org/  tim@tt1.org