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

[Bug 23602] "optional any" is nonsense that should be disallowed

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Aug 2016 13:30:41 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23602-3890-Lh1qT6N3lK@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23602

--- Comment #5 from Boris Zbarsky <bzbarsky@mit.edu> ---
I don't think this got resolved, no.  I never got any feedback from other
implementors on my proposal at
https://lists.w3.org/Archives/Public/public-script-coord/2014JanMar/0176.html
so I just went ahead and implemented a modified version of it in Gecko; see
<https://bugzilla.mozilla.org/show_bug.cgi?id=985536>.  The difference between
what I implemented and the proposal on the list is whether trailing
non-optional "any" affects the argc check behavior....  But in the spec right
now, as far as I can tell, "optional any" can only take on the state "not
passed", and can't have the state "undefined".  That's what I aimed to fix in
my Gecko changes; in Gecko the "optional" bit just affects .length and argc
checks, but the value is always considered "passed" and may just have the value
"undefined".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 29 August 2016 13:30:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 August 2016 13:30:51 UTC