« Bugzilla Issues Index
#811 — 12.6.4: "Perform Binding Instantiation"
- bug_id:
811
- creation_ts:
2012-10-22 17:29:00 -0700
- short_desc:
12.6.4: "Perform Binding Instantiation"
- delta_ts:
2014-06-02 12:41:05 -0700
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 24: April 27, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Allen Wirfs-Brock
- commentid:
1975
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2012-10-22 17:29:27 -0700
In 12.6.4 "The for-in and for-of Statements",
under "Runtime Semantics: Labelled Evaluation",
in the definition of the abstract operation 'For In/Of Body Evaluation',
step 3.e.v.4 says:
Perform Binding Instantiation for lhs passing nextValue and iterationEnv
as arguments.
but this ignores the result returned by Binding Instantiation.
Maybe change to:
Let biResult be the result of performing Binding Instantiation ...
ReturnIfAbrupt(biResult).
- commentid:
1978
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-10-23 16:22:12 -0700
This appears to be intentional as next step explicitly sets the status variable that is used as the equivalent result in the other legs of the case analysis. Need to explain why it is ok/necessary to ignore the actual result of Binding Instantiation.
- commentid:
8496
- comment_count:
2
- who:
Michael Dyck
- bug_when:
2014-05-15 09:25:40 -0700
In rev24, it's at 13.6.4.8 "Runtime Semantics: ForIn/OfBodyEvaluation",
step 3.h.iv.
- commentid:
8497
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-15 09:56:39 -0700
fixed in rev25 editor's draft
- commentid:
8836
- comment_count:
4
- who:
Michael Dyck
- bug_when:
2014-06-02 12:41:05 -0700
confirmed fixed.