« Bugzilla Issues Index
#4074 — 9.2.2.2 OrdinaryCallBindThis: assert that the algorithm will not return an abrupt completion
- bug_id:
4074
- creation_ts:
2015-02-21 14:53:00 -0800
- short_desc:
9.2.2.2 OrdinaryCallBindThis: assert that the algorithm will not return an abrupt completion
- delta_ts:
2015-03-04 18:58:22 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 31: January 15, 2015 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- blocked:
4076
- everconfirmed:
true
- reporter:
Claude Pache
- assigned_to:
Allen Wirfs-Brock
- commentid:
13249
- comment_count:
0
- who:
Claude Pache
- bug_when:
2015-02-21 14:53:15 -0800
9.2.2.2 OrdinaryCallBindThis
The last step of the algorithm, calling envRec.BindThisValue(), is the only one that could end up in an abrupt completion, in case of envrec.[[thisBindingStatus]] is "initialized".
However, (I think) it does not occur, because the OrdinaryCallBindThis abstract operation is always used on newly created execution context with non-initialised this-binding.
Asserting that would be useful, e.g. something like the following, just before current step 8:
Assert: envRec.[[thisBindingStatus]] is "uninitialized", and therefore the next step does not produces an abrupt completion.
- commentid:
13363
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-25 16:02:20 -0800
fixed in rev35 editor's draft
- commentid:
13540
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-04 18:58:22 -0800
fixed in rev35