Closed
Bug 425066
Opened 18 years ago
Closed 14 years ago
Strict mode: 'reference to undefined property' sometimes not given when it should be
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dmandelin, Unassigned)
References
Details
Attachments
(1 file)
|
204 bytes,
text/plain
|
Details |
The attached file shows two cases that appear the same to the programmer, but only one produces the warning.
The branch in the code that makes the difference is in jsobj.c near line 455:
if (!JS_HAS_STRICT_OPTION(cx) ||
(op != JSOP_GETPROP && op != JSOP_GETELEM)) {
return JS_TRUE;
}
In my test file, in the case where no warning appears, the opcode is JSOP_GETLOCALPROP. I suspect JSOP_GETARGPROP, JSOP_GETVARPROP, and JSOP_GETLOCALPROP are also relevant.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•