Closed
Bug 353081
Opened 19 years ago
Closed 15 years ago
Incorrect error message involving "new" and map in "case" expression
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: testcase)
Testing with the "prep patch for plan A, v7b" from bug 346642.
js> x=undefined; switch(x) { case 3: case (new ([3].map)): }
typein:1: TypeError: x is not a function
The error message is incorrect; I'm not trying to treat "x" as a function.
|
Reporter | |
Comment 1•18 years ago
|
||
This bug still exists on trunk.
|
|
Reporter | |
Comment 2•17 years ago
|
||
Bug 420925 might be related.
|
||
Comment 3•15 years ago
|
||
The error has changed on current trunk.
js> x=undefined; switch(x) { case 3: case (new ([3].map)): }
typein:1: TypeError: missing argument 0 when calling function [3].map
|
|
Reporter | |
Comment 4•15 years ago
|
||
I think that's the correct error message. There's an implicit call due to the |new|, and |map| requires arguments. So WFM.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
|
|
Reporter | |
Updated•15 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•