« Bugzilla Issues Index
#2739 — 14.5.17 ClassDefinitionEvaluation: Necessary to preserve evaluation order for static/prototype method definitions?
- bug_id:
2739
- creation_ts:
2014-04-25 05:43:00 -0700
- short_desc:
14.5.17 ClassDefinitionEvaluation: Necessary to preserve evaluation order for static/prototype method definitions?
- delta_ts:
2014-06-16 16:17:17 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 23: April 5, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
7922
- comment_count:
0
- who:
André Bargull
- bug_when:
2014-04-25 05:43:07 -0700
14.5.17 Runtime Semantics: ClassDefinitionEvaluation
All prototype method definitions are evaluated before any static method definition, which breaks source code definition order. This is visible by using computed property names. Is it necessary to preserve original source code definition order?
test case:
---
class C {
static [(print("static def"), "")] () { }
[(print("proto def"), "")] () { }
}
---
Expected output: ?
Actual output: "proto def" and then "static def"
- commentid:
8527
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-16 16:44:23 -0700
fixed in rev25 editor's draft
- commentid:
9018
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-06-16 16:17:17 -0700
fixed in rev25 editor's draft