« Bugzilla Issues Index
#4073 — 4.3.30: "be either"
- bug_id:
4073
- creation_ts:
2015-02-21 14:27:00 -0800
- short_desc:
4.3.30: "be either"
- delta_ts:
2015-03-04 18:58:24 -0800
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 34: February 20, 2015 Release Candidate 1
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
minor
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Allen Wirfs-Brock
- commentid:
13248
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2015-02-21 14:27:24 -0800
In 4.3.30 "property",
it says:
association between a key and a value that is a part of an object.
The key be either a String value or a Symbol value
s|be|is| or s|be|can be|
But doesn't the form of this definition violate ECMA rules?
Maybe it should be more like:
association between a key (either a String value or a Symbol value)
and a value that is a part of an object
- commentid:
13266
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-23 17:39:56 -0800
fixed in rev35 editor's draft
- commentid:
13552
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-04 18:58:24 -0800
fixed in rev35