« Bugzilla Issues Index
#1535 — 8.3.15.1: [[Call]] behaviour for uninitialised function objects not defined
- bug_id:
1535
- creation_ts:
2013-05-31 02:44:00 -0700
- short_desc:
8.3.15.1: [[Call]] behaviour for uninitialised function objects not defined
- delta_ts:
2013-07-15 17:03:18 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 15: May 14, 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:
4114
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-05-31 02:44:30 -0700
Uninitialised function objects do not have a [[Code]] internal property, step 14 of 8.3.15.1 is not yet updated to take this into account. It should probably test for [[Code]] in step 1 and throw a TypeError if [[Code]] is not present.
test case:
(new class extends Function { constructor(){} })()
- commentid:
4276
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-06-21 14:37:51 -0700
Any function with this [[Call]] should have a [[Code]], but it may be unitialized (actually) initialized to undefined. Added a check for that.
fixed in rev 16 editor's draft
- commentid:
4397
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-07-15 17:03:18 -0700
fixed in rev16 draft. July 15, 2013