archives

« Bugzilla Issues Index

#1782 — 10.2.1.2.4: Meaning of "uninitialised binding" unclear for Object Environment Records

• bug_id: 1782
• creation_ts: 2013-08-16 02:44:00 -0700
• short_desc: 10.2.1.2.4: Meaning of "uninitialised binding" unclear for Object Environment Records
• delta_ts: 2015-02-19 19:11:00 -0800
• product: Draft for 6th Edition
• component: technical issue
• version: Rev 16: July 15, 2013 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: 4921
• comment_count: 0
• who: André Bargull
• bug_when: 2013-08-16 02:44:34 -0700

10.2.1.2.4 InitialiseBinding (N,V), steps 2-3:

> 2. Assert: envRec must have an uninitialised binding for N.
> 3. Record that the binding for N in envRec has been initialised.

It is not clear (to me) what "uninitialised binding" means in connection with Object Environment Records. Maybe those two steps were simply copied over from 10.2.1.1.4 (InitialiseBinding for Declarative Environment Records) and don't actually apply to Object Environment Records.

---

• commentid: 4932
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2013-08-16 10:33:48 -0700

Object environment records can, in theory, have uninitialized bindings and it's up to use how you track them.

However, I'm pretty sure that the spec. always creates and then immediately initializes such bindings so the uninitialized state is never observable to ES code. So, in reality you don't actually need to track it.

---

• commentid: 12784
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2015-02-16 13:51:10 -0800

fixed in rev34 editor's draft

added a note to 8.1.1.2.4 pointing out that object env record create binding calls are always immediately followed by an InitializeBinding call.

---

• commentid: 13087
• comment_count: 3
• who: Allen Wirfs-Brock
• bug_when: 2015-02-19 19:11:00 -0800

fixed in rev34