Hi, On Mon, 2005-06-27 at 19:32 +0200, Daniel Bonniot wrote: > > 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. > > I don't know the answer. If somebody can come up with a mauve test... > > In the mean time, my patch improves on the current behavior.
Agreed and there are Mauve tests to proof that. Thanks. I have no idea how this strange case looks like. Since it seems that any "later" class can only be added at the bottom of the class hierarchy. Tom, do you have an example of what you are thinking of? I have checked this in with the following ChangeLog entry: 2005-07-03 Daniel Bonniot <[EMAIL PROTECTED]> * java/io/ObjectStreamClass.java (inSamePackage): New private method. (findAccessibleMethod): Likewise. (cacheMethods): Lookup readResolve and writeReplace using the new findAccessibleMethod(). Thanks Daniel. Cheers, Mark _______________________________________________ Classpath-patches mailing list Classpath-patches@gnu.org http://lists.gnu.org/mailman/listinfo/classpath-patches
