Closed Bug 537849 Opened 15 years ago Closed 13 years ago

Uneval uses "\0" for NUL inappropriately (followed by decimal digit; becomes octal)

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 430927

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: testcase)

js> "\0" + "0" "\00" js> "\00" "\0" js> "\0" + "3" "\03" js> "\03" "\x03" I think it's uneval that's screwing up here. ECMA-262 5th edition, 7.8.4 "String literals", says stuff about "\0 [lookahead ∉ DecimalDigit]". This bug was found by a part of jsfunfuzz intended to test tracing of type-unstable recursion!
Summary: Uneval uses "\0" inappropriately (followed by decimal digit) → Uneval uses "\0" for NUL inappropriately (followed by decimal digit; becomes octal)
The output has changed a bit, but still broken. js> "\0" + "0" "\x000" js> "\00" "\x00" js> "\0" + "3" "\x003" js> "\03" "\x03"
OS: Mac OS X → All
Or maybe the new behavior is correct?
I could have sworn I closed this as a dup yesterday...
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Oh, I closed bug 621119 as fixed. They're all the same issue in the end, doesn't really matter whether as dup or as fixed.
You need to log in before you can comment on or make changes to this bug.