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

Re: Removing the concept of "optional any"

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 05 Mar 2014 09:36:18 -0500
Message-ID: <53173662.9000807@mit.edu>
To: Domenic Denicola <domenic@domenicdenicola.com>, Allen Wirfs-Brock <allen@wirfs-brock.com>, "Mark S. Miller" <erights@google.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 2/19/14 12:26 PM, Boris Zbarsky wrote:
> If so, it seems like that behavior would more or less map to:
>
> 1)  "any" is allowed, affects .length if trailing, accepts all ES
> values, does NOT trigger an argc check.  Defaults to undefined if not
> passed explicitly.
>
> 2)  "optional any" is allowed, does not affect .length if trailing,
> accepts all ES values, defaults to the provided default value, or
> undefined if no default value is provided, if not passed explicitly.

So does this make sense to people?  I'd like to actually move forward 
here, one way or another.

-Boris
Received on Wednesday, 5 March 2014 14:36:50 UTC

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