JDK-6182000 : StringBuilder javadoc doesn't match source code.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-10-20
  • Updated: 2010-04-02
  • Resolved: 2004-10-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0Resolved
Related Reports
Relates :  
JDK-5023741 - getSuperclass returns AbstractStringBuilder instead of Object
Relates :  
JDK-4780441 - stddoclet: Incorrectly documents inherited members from package-private class
Description
FULL PRODUCT VERSION :
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)

A DESCRIPTION OF THE PROBLEM :
The javadoc for java.lang.StringBuilder says that StringBuilder extends Object.  The source code shows that StringBuilder extends AbstractStringBuilder.  No javadoc exists for AbstractStringBuilder.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Look at javadoc.  Look at source.
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/StringBuilder.html

REPRODUCIBILITY :
This bug can be reproduced always.
###@###.### 10/20/04 18:26 GMT
Comments
EVALUATION That StringBuilder extends AbstractStringBuilder is an implementation detail of StringBuilder, not a part of its exported API. The format in which the Standard Doclet presents inheritence information ("extends Object") is certainly a bit misleading: you should read that as stating only that Object is extended, but not necessarily directly. A further discussion of this issue can be found in the javadoc bug report 4780441. ###@###.### 10/20/04 22:39 GMT
20-10-2004