Re: May the defineProperty method of a proxy handler throw a TypeError?

On Wed, Aug 10, 2011 at 7:20 PM, Cameron McCormack wrote: > On 9/08/11 9:40 AM, Mark S. Miller wrote: > >> If there are no show-stopping legacy compat constraints forcing us to >> specify Reject, I prefer that we specify these to throw a TypeError. >> > > I can't say for sure, but I would be surp

Re: May the defineProperty method of a proxy handler throw a TypeError?

On 9/08/11 9:40 AM, Mark S. Miller wrote: If there are no show-stopping legacy compat constraints forcing us to specify Reject, I prefer that we specify these to throw a TypeError. I can't say for sure, but I would be surprised if this didn't cause problems, given that it introduces exception

Re: Internationalization API spec draft

I'll add a link to your document to the doc I sent couple days ago(which already has some comments). 10. август 2011. 17.43, Norbert Lindenberg је написао/ла: > I thought it would be useful to convert the results of

Internationalization API spec draft

I thought it would be useful to convert the results of our discussion on 2011-07-26 into spec language and see how it holds up. In the process I found and filled several gaps, made a few changes, and noted various issues. The result, so far limited to NumberFormat and its prerequisites, is here:

Re: Regexp backreferences

Thanks for the replies Dave and Gavin, and the data in particular. Looks like we'll leave it as is. Paul On Tue, Aug 9, 2011 at 14:18, Dave Fugate wrote: > Hi Paul, both of these tests were disabled on test262 about a month ago (see > https://bugs.ecmascript.org/show_bug.cgi?id=120).  In brief,

Re: An experiment using an object literal based class definition pattern

On Aug 10, 2011, at 7:28 AM, Axel Rauschmayer wrote: > So the consensus is to start with the simplest possible class literal? I > don’t think we currently need much more than object literal syntax + sections > + subclassing. No, the class syntax includes a body which is *not* an object literal.

Re: An experiment using an object literal based class definition pattern

I find the following points remarkable about Allen’s proposal: - The <| operator creates prototype chains for both prototypes and constructors. This introduces an important symmetry. - The merge operator obj.{…} makes object literals usable in many more contexts. So the consensus is to start with

Re: July TC39 meeting notes, day 1

On 9 August 2011 19:25, Kevin Reid wrote: > On Tue, Aug 9, 2011 at 01:17, Andreas Rossberg wrote: >> On 8 August 2011 18:46, Kevin Reid wrote: >>> On Mon, Aug 8, 2011 at 08:50, Andreas Rossberg wrote: Arguably, making a proxy trap return getters/setters seems a somewhat pointless use