On 3/15/06, Stuart Ballard <stuart.a.ballard@xxxxxxxxx> wrote:
> Or Javadoc is treating deprecation as if it inherits from the class to
> its constructor. More research needed...
A test run of Sun's javadoc confirms that it treats all members of a
deprecated class as deprecated; I've made this change to my local
japitools and I'll try to get it committed in time for tonight's run.
Could someone confirm that gjdoc correctly emulates this approach?
Interestingly, Sun's javadoc gets a little schizophrenic with inner
classes of deprecated classes: if you have code like this:
/**
* @deprecated
*/
public class Outer {
public class Inner {
}
}
the javadoc for Outer will list Inner as a *deprecated* inner class,
but the javadoc for Inner will state that it's not deprecated at all.
This suggests that we might want an Eclipse warning when a deprecated
class has a non-deprecated inner class, because it leads to
inconsistent documentation.
Not sure what gjdoc should do in this case, but I definitely think it
should issue some kind of warning too :)
For japitools, I've punted on this problem and said that inner classes
of deprecated classes aren't deprecated unless explicitly marked as
such.
> Japi's supposed to consider replacing a nongeneric type with something
> that erases to that type as okay.
Still looking into this one. Keep 'em coming!
Stuart.
--
http://sab39.dev.netreach.com/
