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

Re: [WebIDL] interface objects with [Constructor] and [[Call]]

From: Cameron McCormack <cam@mcc.id.au>
Date: Fri, 8 Oct 2010 16:07:07 +1300
To: "Mark S. Miller" <erights@google.com>
Cc: Maciej Stachowiak <mjs@apple.com>, James Graham <jgraham@opera.com>, Travis Leithead <travil@microsoft.com>, Simon Pieters <simonp@opera.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, annevk@opera.com
Message-ID: <20101008030707.GL16750@wok.mcc.id.au>
The spec currently requires a TypeError to be thrown, just because there
is no [[Call]] defined for interface objects.  I was going to say that I
agreed with the reasoning from Maciej and Jonas, but this argument has
swayed me the other way:

Mark S. Miller:
> When a normal function F ignores its "this" and returns an object, prefixing
> a call to F with "new" results in no change in behavior. When there are no
> legacy compat issues saying otherwise, I think this is how new
> functions-which-make-things should be defined.

I haven’t made the change yet, but I have made a note in the spec to do

Cameron McCormack ≝ http://mcc.id.au/
Received on Friday, 8 October 2010 03:07:56 UTC

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