Closed Bug 379519 Opened 18 years ago Closed 15 years ago

Mysterious sharp variable declaration when uneval'ing an object with E4X

Categories

(Core :: JavaScript Engine, defect)

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

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jruderman, Assigned: Waldo)

Details

(Keywords: testcase)

js> j = uneval({x: <x><y/></x>}) ({x:#1=<x> <y/> </x>}) js> eval(j) typein:15: SyntaxError: invalid sharp variable definition: typein:15: </x>}) typein:15: ...^ This might be two bugs: the first statement shouldn't cause sharp variable output, and the second statement should be accepted as a legitimate use of a sharp variable.
jwalden: Ever get a chance to look at this?
Sure, I'll take a look.
Assignee: general → jwalden+bmo
I think this is resolved/fixed in latest tracemonkey, (possibly duplicate of bug 335051 and bug 380946).
Yep, WFM on TM tip.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
(Both parts!)
You need to log in before you can comment on or make changes to this bug.