« Bugzilla Issues Index
#2197 — 14.1.14: function name passed to FunctionCreate instead of calling SetFunctionName
- bug_id:
2197
- creation_ts:
2013-11-04 09:08:00 -0800
- short_desc:
14.1.14: function name passed to FunctionCreate instead of calling SetFunctionName
- delta_ts:
2013-11-08 13:09:10 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 20: October 28, 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:
6451
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-11-04 09:08:57 -0800
14.1.14 Runtime Semantics: InstantiateFunctionObject, step 3.
14.1.15 Runtime Semantics: Evaluation, FunctionExpression : function BindingIdentifier, step ?.
14.3.8 Runtime Semantics: DefineMethod, step 6a.
14.3.9 Runtime Semantics: PropertyDefinitionEvaluation, MethodDefinition : get PropertyName ( ), step 7a.
14.3.9 Runtime Semantics: PropertyDefinitionEvaluation, MethodDefinition : set PropertyName ( PropertySetParameterList ), step 6a.
These algorithms pass the function's name to FunctionCreate, but FunctionCreate does not actually use the "methodName" parameter in this context. Instead of passing the name to FunctionCreate, call SetFunctionName?
- commentid:
6456
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-11-04 11:13:40 -0800
fixed in rev21 editor's draft
- commentid:
6554
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-11-08 13:09:10 -0800
fixed in rev21 draft