Closed
Bug 293958
Opened 20 years ago
Closed 19 years ago
"(100.0 * Number.MIN_VALUE).toPrecision (12);" fails
Categories
(Rhino Graveyard :: Core, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sweeks, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
2.54 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
The statement causes StringIndexOutOfBoundsException.
Reproducible: Always
Comment 1•20 years ago
|
||
I've fixed this -- I refactored the stripping of trailing zeroes into a
separate method, as it is performed from more than one place.
There are still some rough edges with my CVS access, so I can't commit this
myself at the moment.
Comment 2•20 years ago
|
||
Any objections to me committing this?
Comment 3•20 years ago
|
||
(In reply to comment #2)
> Any objections to me committing this?
Not an objection, but rather observation: the patch makes some cases where Rhino
currently hits the exception to go to infinite loop due to other bugs in DTOA
code. Fixing those bugs can trigger redesign of the whole code and in a longer
term the patch can be irrelevant.
Comment 4•20 years ago
|
||
(In reply to comment #3)
> Not an objection, but rather observation: the patch makes some cases where
Rhino
> currently hits the exception to go to infinite loop due to other bugs in DTOA
> code. Fixing those bugs can trigger redesign of the whole code and in a longer
> term the patch can be irrelevant.
Hm - I was unaware of these other bugs. Regardless, until those other bugs are
fixed, the current patch would still improve the existing situation, wouldn't
it? So the question is, do you see sense in committing this patch until the
other bugs are tackled? (Your observation would suggest your opinion is that it
does not, but you weren't explicit about it :-) )
Comment 5•20 years ago
|
||
The original fix for the bug was itself buggy -- an occurrence of the "!="
operator should have been "==" instead :-[
Updated•20 years ago
|
Attachment #188968 -
Attachment is obsolete: true
Comment 6•19 years ago
|
||
Reassigning to please_see_bug_288433@eml.cc pending resolution of bug 288433
Assignee: igor.bukanov → please_see_bug_288433
Updated•19 years ago
|
Assignee: please_see_bug_288433 → nobody
Updated•19 years ago
|
Status: NEW → ASSIGNED
Comment 7•19 years ago
|
||
Committed the fix to CVS.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•