« Bugzilla Issues Index
#1187 — default constructor: `super.constructor` is over-constrained
- bug_id:
1187
- creation_ts:
2012-12-30 12:37:00 -0800
- short_desc:
default constructor: `super.constructor` is over-constrained
- delta_ts:
2013-03-08 14:44:22 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 13: December 21, 2012 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Herbert Vojčík
- assigned_to:
Allen Wirfs-Brock
- commentid:
3107
- comment_count:
0
- who:
Herbert Vojčík
- bug_when:
2012-12-30 12:37:01 -0800
In 13.5, "Runtime Semantics: ClassDefinitionEvaluation", item 7 stands:
If constructor is empty, then
a. Let constructor be the result of parsing the String "constructor(... args){super.constructor(...args);}" using the syntactic grammar with the goal symbol MethodDefinition.
I think "super.constructor" is overconstrained, it would be more generic and future-friendly, if that would be
If constructor is empty, then
a. Let constructor be the result of parsing the String "constructor(... args){super(...args);}" using the syntactic grammar with the goal symbol MethodDefinition.
The effect is the same, as things stand now.
- commentid:
3296
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-03-06 17:14:48 -0800
fixed in rev 14 editor's draft
- commentid:
3358
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-03-08 14:44:22 -0800
in Rev 14 draft