archives

« Bugzilla Issues Index

#795 — 11.2.6: semantics of X are like Y but different

• bug_id: 795
• creation_ts: 2012-10-15 13:06:00 -0700
• short_desc: 11.2.6: semantics of X are like Y but different
• delta_ts: 2012-10-26 15:34:25 -0700
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 10: September 27, 2012 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: Michael Dyck
• assigned_to: Allen Wirfs-Brock

---

• commentid: 1934
• comment_count: 0
• who: Michael Dyck
• bug_when: 2012-10-15 13:06:56 -0700

In 11.2.6 "Tagged Templates",
under "Runtime Semantics",
it says:
The runtime semantics of production:
CallExpression : CallExpression TemplateLiteral
is identical to that of
MemberExpression: MemberExpression TemplateLiteral
but with evaluation of CallExpression substituted for the evaluation of
MemberExpression.

Given that the semantics in question is one simple 3-step algorithm,
it might be better to just state it in full (under "Runtime Semantics:
Evaluation").

Note that the latter approach is used in two other places where the semantics differ by a single 'CallExpression' vs 'MemberExpression':
11.2 Left-Hand-Side Expressions / Static Semantics: Contains
11.2.3 Function Calls / Runtime Semantics: Evaluation

(On the other hand, the former approach is still used by:
11.2.1 Property Accessors / Runtime Semantics: Evaluation
but there the semantics are a 10-step algorithm.)

---

• commentid: 2045
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2012-10-25 15:06:35 -0700

corrected in rev 11 editor's draft

---

• commentid: 2161
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2012-10-26 15:34:25 -0700

in October 26, 2012 release draft