"John Keiser" <[EMAIL PROTECTED]> writes:
> > From: Maxim Kizub [mailto:[EMAIL PROTECTED]]
> > Subject: Re: Excellent News About java.io
> >
> >
> > >As I think we told Stuart, those items you're talking about (overriding a
> > >method when the spec doesn't override) are entirely OK to do. Spec
> > >compatibility means conforming to the APIs, period.
> >
> >
> > Hello.
> >
> > I don't know about classes and methods you mean. Sometimes this
> > is ok. But be carefull about "super.foo()" constructions.
> >
>
> We control all the classes from Object on down, so super.foo() should not be
> a problem. We'll know if we insert or remove a class in the inheritance
> tree, which is what I presume you're talking about.
>
> As long as *any* method is syntactically identical (same modifiers, name,
> arguments) and functionally identical to the spec, it is conformant to the
> public Java API. If no difference can possibly be detected, then for the
> purposes of those doing the detecting, there is no difference.
The only way to detect this as _not_ different is to identify the
inherited functions and ignore them where we overload and Sun doesn't.
Should I look into this?
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |------------------------------
