W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

[Bug 15986] Specify exactly how and when ECMAScript arguments are evaluated

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Feb 2012 17:35:30 +0000
To: public-script-coord@w3.org
Message-Id: <E1RxMHq-0006Fa-Ri@jessica.w3.org>

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> 2012-02-14 17:35:30 UTC ---
There are two places that evaluate arguments in WebIDL.  One is the argument
resolution algorithm at
http://dev.w3.org/2006/webapi/WebIDL/#dfn-argument-resolution-algorithm and is
defined to go one by one.

The other is the overload resolution algorithm, and the order it examines the
arguments in depends on the precise overload set right now (because some IDL
argument types require that the actual passed-in argument be examined and some
do not, as far as I can tell).  It doesn't evaluate things per se, but it can
return a null overload set after examining only some of the arguments, so can
prevent entry into the argument resolution algorithm altogether.

So this is all specified already.  The question is whether the specification
makes sense.  For example, does it make sense to run the overload algorithm on
overload sets of size 1 to start with?

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 14 February 2012 17:35:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:05 UTC