harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Tromey <tro...@redhat.com>
Subject Re: Writing JavaDoc
Date Fri, 13 Jan 2006 20:50:53 GMT
>>>>> "Mikhail" == Loenko, Mikhail Y <mikhail.y.loenko@intel.com> writes:

Mikhail> I think Classpath is a little bit different story. It is not
Mikhail> a Java(tm) so a developer who writes for Classpath has to
Mikhail> validate with Classpath docs whether his code is going to
Mikhail> work.

The real reason we write javadoc is completeness.  Suppose an OS ships
a Classpath-based VM and the user wants to look at the core javadoc in
Eclipse.  It isn't acceptable to us for him to have to download the
proprietary JDK to accomplish this.

As far as Sun's javadoc goes... in my experience you can't really call
it a "spec" with a straight face.  It omits far too much.


View raw message