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: Mon, 20 Feb 2012 18:51:23 +0000
To: public-script-coord@w3.org
Message-Id: <E1RzYKZ-0007vd-G9@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15986

--- Comment #18 from Aryeh Gregor <ayg@aryeh.name> 2012-02-20 18:51:20 UTC ---
So basically we'd require that any pair of operations on the same interface
with the same name must require a different number of arguments.  For instance,
foo(int a, optional int b) cannot coexist with any other operation named "foo"
that takes one or two arguments, but could coexist with one that takes zero, or
three.  That would mean the overload resolution algorithm could be scrapped,
and it looks like no new prose would be needed anywhere.  Then this bug is easy
to resolve.  Sounds like a win-win situation to me.

-- 
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 Monday, 20 February 2012 18:51:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC