Closed
Bug 438339
Opened 16 years ago
Closed 16 years ago
looking up null different in TT
Categories
(Tamarin Graveyard :: Tracing Virtual Machine, defect)
Tamarin Graveyard
Tracing Virtual Machine
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: treilly, Assigned: stejohns)
Details
Attachments
(2 files)
var o = {}; trace(o[null]); In TC: undefined In TT: ReferenceError: Error #1081: Property null not found on Object and there is no default value. at global$init()
Assignee | ||
Comment 1•16 years ago
|
||
also broken: var o = []; trace(o[null]); and ditto for "undefined" for the key.
Assignee | ||
Comment 2•16 years ago
|
||
bug actually is that dynamic lookups weren't correct for keys of type null, undefined, boolean, or namespace. fix is in the works. obviously we need to add an acceptance test for this, I'll do one of those too.
Assignee | ||
Comment 3•16 years ago
|
||
box2dynamevec was simply rejecting keys of type null/void/bool/ns; it should have converted them to interned strings.
Assignee | ||
Comment 4•16 years ago
|
||
Acceptance test, since existing sanities didn't catch this
Attachment #324509 -
Flags: review?(treilly)
Reporter | ||
Updated•16 years ago
|
Attachment #324501 -
Flags: review?(treilly) → review+
Reporter | ||
Updated•16 years ago
|
Attachment #324509 -
Flags: review?(treilly) → review+
Assignee | ||
Comment 5•16 years ago
|
||
pushed as changeset: 393:58fb13dc90c8
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•