archives

« Bugzilla Issues Index

#556 — "Establish and enter a new execution context."

• bug_id: 556
• creation_ts: 2012-07-14 22:21:00 -0700
• short_desc: "Establish and enter a new execution context."
• delta_ts: 2012-07-14 22:37:46 -0700
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 9: July 8, 2012 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: INVALID
• priority: Normal
• bug_severity: normal
• everconfirmed: true
• reporter: Michael Dyck
• assigned_to: Allen Wirfs-Brock

---

• commentid: 1340
• comment_count: 0
• who: Michael Dyck
• bug_when: 2012-07-14 22:21:57 -0700

13.5.1 "[[Call]]" / step 3
14 "Program" / Runtime Semantics: Program Evaluation / step 3
15.1.2.1 "eval (x)" / step 3

Each of these uses the instruction
"Establish and enter a new execution context"

I believe that in 13.5.1, this is supposed to define the variable 'calleeContext', and in 14, the variable 'progCxt', which are not explicitly defined.

So, to make things explicit, it would be better to use phrasing like:
"Let calleeContext be a new execution context."

15.1.2.1 doesn't use a variable to refer to the new execution context, but maybe it would be better if it did. (Certainly, it would be more consistent with 13.5.1 and 14.)

---

• commentid: 1341
• comment_count: 1
• who: Michael Dyck
• bug_when: 2012-07-14 22:37:46 -0700

Sorry, my mistake. I was looking at the wrong thing.