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

Re: an idea for replacing arguments.length

From: Brendan Eich <brendan@mozilla.com>
Date: Tue, 12 Nov 2013 09:21:30 -0800
Message-ID: <5282639A.9060908@mozilla.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Allen Wirfs-Brock <allen@wirfs-brock.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss@mozilla.org
Boris Zbarsky wrote:
> On 11/12/13 11:24 AM, Brendan Eich wrote:
>> Yeah, why are *new* (this is from Web Events, not legacy) APIs doing the
>> crazy. Answer: because people imitate older crazy APIs, and WebIDL
>> supports this.
>
> No.  In this case it's because the spec started out one way (with the 
> sequence, iirc) but then got changed to the other way, but 
> implementations had already shipped the first way, so now for compat 
> they support both.

Oh, ok -- new-ish legacy. This makes the case for stronger normative 
specs against such overloading, starting with WebIDL.

> If webidl didn't allow this, they'd just use "any..." and define it 
> all in prose, I assume.

Perhaps, and that raises a good point: JS allows all kinds of bad 
overloading. Doesn't mean we should encourage it in the WebIDL-based 
specs, though.

/be
Received on Tuesday, 12 November 2013 17:21:58 UTC

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