Closed
Bug 508637
Opened 16 years ago
Closed 16 years ago
Get rid of strict warning on trailing commas in object initializers (as per ES5)
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla1.9.2b1
People
(Reporter: davida, Assigned: jimb)
References
Details
Attachments
(1 file)
|
1.74 KB,
patch
|
igor
:
review+
|
Details | Diff | Splinter Review |
given:
foo = {bar: 'baz',
tom: 'cat',
}
me:
>>> What's the rationale for complaining
>>> about that? I find that the trailing comma makes patches cleaner, and is
>>> less error prone (the cost of forgetting a comma is potentially large).
shaver:
>> ECMA's syntax doesn't permit a trailing comma in object initializers
>> (perhaps changed in ES5, I can't recall)
brendan:
> ES5 indeed gets rid of this obnoxious MSFT contribution to ES3. :-)
> Someone please file a bug to get rid of this strict warning.
Comment 2•16 years ago
|
||
Jim, Rob: this is trivial to fix and wanted for ES5 conformance.
/be
Blocks: es5
Flags: wanted1.9.2?
| Assignee | ||
Updated•16 years ago
|
Assignee: general → jim
| Assignee | ||
Comment 3•16 years ago
|
||
Attachment #393016 -
Flags: review?(igor)
Updated•16 years ago
|
Attachment #393016 -
Flags: review?(igor) → review+
| Assignee | ||
Comment 4•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Flags: wanted1.9.2?
Target Milestone: --- → mozilla1.9.2b1
Version: unspecified → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•