« Bugzilla Issues Index
#3703 — 19.2.1.1.1 CreateDynamicFunction: Unreachable steps
- bug_id:
3703
- creation_ts:
2015-01-31 08:03:00 -0800
- short_desc:
19.2.1.1.1 CreateDynamicFunction: Unreachable steps
- delta_ts:
2015-02-26 02:53:45 -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:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
11776
- comment_count:
0
- who:
André Bargull
- bug_when:
2015-01-31 08:03:02 -0800
19.2.1.1.1 RuntimeSemantics: CreateDynamicFunction(constructor, newTarget, kind, args)
The following steps are no longer reachable after the constructor reform.
- step 18 (FunctionAllocate is infallible)
- step 22 (FunctionInitialize is infallible)
- step 24.b (ObjectCreate is infallible)
- step 26 (MakeConstructor is infallible)
- steps 27-28 (HasOwnProperty always returns false)
- step 29 condition (see above)
- step 29.b (SetFunctionName is infallible)
- commentid:
11878
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-02 10:53:46 -0800
fixed in rev32 editor's draft.
Except, note that all operations that allocate new object can potentially result in abrupt completions. Admittedly, the spec. is rather sloppy about that case and it's plausible that most simple object allocation will always succeed.
- commentid:
12013
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-02 18:39:00 -0800
fixed in rev32 draft
- commentid:
13384
- comment_count:
3
- who:
André Bargull
- bug_when:
2015-02-26 02:53:45 -0800
ReturnIfAbrupt after FunctionAllocate and ObjectCreate is still present.