Closed Bug 646600 Opened 14 years ago Closed 13 years ago

Incorrect behavior (and decompilation) when sharps are nearby

Categories

(Core :: JavaScript Engine, defect)

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

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: testcase)

This was caught by jsfunfuzz round-trip checking. js> (function() { var a = [1,,,]; return a; })() [1, , ,] Correct js> (function() { var a = [1,,,]; return a; }) (function () {var a = [1, , , ];return a;}) Correct js> (function() { var a = [1,,,]; return a; var b = #1#; })() [1] Missing all the holes js> (function() { var a = [1,,,]; return a; var b = #1#; }) (function () {var a = [1, , ];return a;var b = #1#;}) Missing one of the holes
OS: Mac OS X → All
Hardware: x86 → All
Fixed by bug 566700, the removal of sharp variables.
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.