W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

[Bug 22947] Operation functions should not have a prototype property

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Aug 2013 14:46:45 +0000
To: public-script-coord@w3.org
Message-ID: <bug-22947-3890-BR9225RDAQ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22947

Mark S. Miller <erights@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erights@gmail.com

--- Comment #3 from Mark S. Miller <erights@gmail.com> ---
(In reply to comment #2)
> Functions have a prototype property by default. I would like the spec to
> point out that the functions backing operations are not normal functions and
> should not have a prototype (same for the getter and setter functions).

I agree they should not have a prototype property or a [[Construct]] internal
method. But I would avoid the phrase "not normal functions". In ES3 and ES5,
all non-constructor Chapter 15 functions are of this form. In ES6, arrow
functions are as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 20 August 2013 14:46:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC