Closed
Bug 375641
Opened 19 years ago
Closed 13 years ago
Function decompilation throws away high bytes of characters in regexp literals
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase)
Function decompilation screws up when unicode characters appear in regular expression literals:
js> uneval(uneval(eval("(function () { return /\u3059/ })")))
"(function () {return /Y/;})"
In contrast, it works fine for direct uneval of a regexp:
js> uneval(uneval(eval("/\u3059/")))
"/\u3059/"
Updated•14 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Reporter | ||
Comment 2•14 years ago
|
||
This is especially nasty when it collapses to the null character:
js> eval("(function() { /\u3000/.exec(s) })")
(function () {/.exec(s);})
js> eval("(function() { /\u0000/.exec(s) })")
(function () {/.exec(s);})
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•