>>>>> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes:
>> > I wonder if there is a strange case here where someone adds a private
>> > method to the class hierarchy "later" (after all the other classes are
>> > compiled). Should the private method hide the superclass methods of
>> > the same signature? Perhaps this is an incompatible change, offhand I
>> > forget.
Mark> Agreed and there are Mauve tests to proof that. Thanks.
Mark> I have no idea how this strange case looks like. Since it seems that any
Mark> "later" class can only be added at the bottom of the class hierarchy.
Mark> Tom, do you have an example of what you are thinking of?
Suppose you have a hierarchy like:
class A { blah blah readResolve() }
class B extends A { }
class C extends B { }
You compile all of these.
Then you go back and add 'private ... readResolve()' to B.
Should C now really be using A's readResolve()?
Tom
_______________________________________________
Classpath-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath-patches
