Closed Bug 124508 Opened 23 years ago Closed 22 years ago

regexp.lastIndex should be integer-valued double, not uint32

Categories

(Rhino Graveyard :: Core, defect)

Product:
Rhino Graveyard
Component:
Core
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: pschwartau, Assigned: rogerl)

Details

This is the Rhino version of bug 124339 against SpiderMonkey.
The relevant testcase is an old one:

        mozilla/js/tests/ecma_2/RegExp/properties-002.js

Five new cases ranging between Math.pow(2,32) and Number.MAX_VALUE
have now been added to the testcase to cover the range between the
uint32 upper bound and the upper bound for doubles. These new cases
are failing in Rhino:


*-* Testcase ecma_2/RegExp/properties-002.js failed:

Failure messages were:
/\B/.lastIndex = 0 FAILED! expected: 4294967296
/\B/.lastIndex = 1 FAILED! expected: 4294967297
/\B/.lastIndex = 0 FAILED! expected: 8589934592
/\B/.lastIndex = 0 FAILED! expected: 1099511627776
/\B/.lastIndex = 0 FAILED! expected: 1.7976931348623157e+308
Fix checked in - new engine implementation ported from SpiderMonkey.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Verified Fixed - the above testcase now passes in the rhino, rhinoi shells.
Status: RESOLVED → VERIFIED
Targeting as resolved against 1.5R4
Target Milestone: --- → 1.5R4
You need to log in before you can comment on or make changes to this bug.