🚀 go-pugleaf

I'd be interested to hear what alternatives there are. Throwing a
compile error would be yet a worse solution. The only true problem it
causes is when there are different implementations necessary for each
of the operations. And while this could be a problem, it's never
surfaced on any of the teams I've worked with.

Kirk Knoernschild
Senior Consultant/Instructor
TeamSoft, Inc.
Mentoring, Training, Consulting
www.teamsoftinc.com
www.kirkk.com

"Tristan Reeves" <moonshine@apex.net.au> wrote in message news:<1024283082.192985@web.apex.net.au>...
> Hi,
> 
> I am fairly new to Java, and I am sure this question has been raised on
> numerous occasions. Nevertheless...
> 
> I was saddened to find out that Java fails miserably in implemeting multiple
> interfaces which share a method signature. I know the standard contorsion of
> using inner classes, one for each interface, have the inner classes delegate
> to a method on the outer class, and then allowing access to instances of
> these inner classes via an accessor method on the outer class.
> 
> Does anyone know if there are any plans to fix this ridiculous state of
> affairs? Or, is there any other way to resolve name-clashes?
> 
> Regards,
> Tristan.