Bug ID: JDK-5026712 Constant Field Values doc inconsistent with Float.MAX_VALUE and MIN

Type: Bug
Component: tools
Sub-Component: javadoc(tool)
Affected Version: 1.4.2

Priority: P4
Status: Closed
Resolution: Duplicate
OS: windows_2000
CPU: x86

Submitted: 2004-04-05
Updated: 2005-01-25
Resolved: 2005-01-25


Name: rmT116609			Date: 04/05/2004


A DESCRIPTION OF THE PROBLEM :
The Constant Field Values doc at http://java.sun.com/j2se/1.4.2/docs/api/constant-values.html and elsewhere is inconsistent with the actual values for Float.MAX_VALUE and Float.MIN_VALUE.

The doc says:
public static final float MAX_VALUE 3.4028234663852886E38f
public static final float MIN_VALUE 1.401298464324817E-45f

The source code and behavior is:
    public static final float MAX_VALUE = 3.4028235e+38f;
    public static final float MIN_VALUE = 1.4e-45f;



REPRODUCIBILITY :
This bug can be reproduced always.


(Incident Review ID: 246379) 
======================================================================

EVALUATION java.lang.Float values in http://java.sun.com/j2se/1.4.2/docs/api/constant-values.html and elsewhere are inconsistent with the actual values for Float.MAX_VALUE and Float.MIN_VALUE. ###@###.### 2004-04-10 There are an infinite number of strings which should be mapped to a given floating-point value since there is a nonzero length segment of the real number line which will be rounded to a given floating-point value. Both the short strings in the JavaDoc for Float.{MAX, MIN}_VALUE and the longer strings in the constant field page will be converted to the proper value; see the program in comments. The shorter strings are more correct in the sense that they have the "shortest string needed for roundtrip conversion" property. The constant field values appear to written out in double precision. Therefore the bug, if any, is with the standard doclet and not the core libraries; transfering the bug accordingly. ###@###.### 2005-1-25 01:42:44 GMT

25-01-2005