« Bugzilla Issues Index
#2559 — Need to define what "is not present" tests for arguments mean
- bug_id:
2559
- creation_ts:
2014-02-20 09:13:00 -0800
- short_desc:
Need to define what "is not present" tests for arguments mean
- delta_ts:
2014-04-06 11:31:18 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 22: January 20, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Boris Zbarky
- assigned_to:
Allen Wirfs-Brock
- commentid:
7380
- comment_count:
0
- who:
Boris Zbarky
- bug_when:
2014-02-20 09:13:04 -0800
In particular, need to define that these are arguments.length checks and that they supersede the normal "missing means undefined" rule.
- commentid:
7448
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-03-18 15:50:38 -0700
How about this in clause 17, 4th paragraph (last sentence is new):
Unless otherwise specified in the description of a particular function, if a built-in function or constructor is given fewer arguments than the function is specified to require, the function or constructor shall behave exactly as if it had been given sufficient additional arguments, each such argument being the undefined value. Such missing arguments are considered to be “not present” and may be identified in that manner by specification algorithms.
fixed in rev23 editor's draft
- commentid:
7449
- comment_count:
2
- who:
Boris Zbarky
- bug_when:
2014-03-18 18:53:37 -0700
That helps a lot, yes.
- commentid:
7596
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2014-04-06 11:31:18 -0700
fixed in rev23 draft