Closed
Bug 366700
Opened 18 years ago
Closed 18 years ago
CheckFinalReturn issues a strict warning without regard to strict flag
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INVALID
People
(Reporter: crowderbt, Assigned: crowderbt)
Details
Attachments
(1 file)
|
1.17 KB,
patch
|
Details | Diff | Splinter Review |
Attached is the proposed patch. I -think- house style recommends the addition of the clarifying parenthesis as I've done here, but I couldn't find a specific reference in the SpiderMonkey coding style doc on the wiki.
Attachment #251191 -
Flags: review?(brendan)
|
Assignee | |
Comment 1•18 years ago
|
||
Actually, this bug is bogus, disregard.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Updated•18 years ago
|
Attachment #251191 -
Flags: review?(brendan)
|
||
Comment 2•18 years ago
|
||
Comment on attachment 251191 [details] [diff] [review] JS_HAS_STRICT_OPTION check No, we don't parenthesize == against && or || -- C ain't Pascal ;-). /be
You need to log in
before you can comment on or make changes to this bug.
Description
•