Closed
Bug 557277
Opened 15 years ago
Closed 6 years ago
Number.MIN_VALUE is looser than in ES3 due to denormal issues
Categories
(Tamarin Graveyard :: Documentation, defect, P4)
Tamarin Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
WONTFIX
Q1 12 - Brannan
People
(Reporter: lhansen, Assigned: rwhitley)
Details
(Whiteboard: AS3 Language)
See bug #555805. IEEE arithmetic or no, we don't want to state unequivocally that MIN_VALUE is the smallest IEEE 64-bit denormal, rather we want to state what Stan suggests:
"I think we want the following two things to be true:
Min value is not zero: Number.MIN_VALUE > 0
and
All smaller values (eg MIN_VALUE/2) are zero: Number.MIN_VALUE/2 == 0"
Currently our on-line documentation states this, which is too specific:
"The smallest representable non-negative, non-zero, number (double-precision IEEE-754). This number is approximately 5e-324."
Comment 1•15 years ago
|
||
How about something like "The smallest representable non-negative, (double-precision
IEEE-754) number that does not compare equal to zero. This number usually is approximately 5e-324 but can be larger on systems that do not support denormalized numbers."
Assignee: nobody → djacowit
Flags: flashplayer-qrb+
Priority: -- → P4
Target Milestone: --- → flash10.2
Updated•14 years ago
|
Target Milestone: Q3 11 - Serrano → Q1 12 - Brannan
Comment 2•6 years ago
|
||
Tamarin is a dead project now. Mass WONTFIX.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 3•6 years ago
|
||
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
You need to log in
before you can comment on or make changes to this bug.
Description
•