Draft of Function.prototype.bind.
Allen.Wirfs-Brock at microsoft.com
Thu Nov 6 17:23:39 PST 2008
Note that appendices C, D, and E are not particularly complete or up to date. This is something we are going to try to work on between now and Kona as I believe that these summaries are very important to understanding the overall impact of ES3.1
> -----Original Message-----
> From: es3.x-discuss-bounces at mozilla.org [mailto:es3.x-discuss-
> bounces at mozilla.org] On Behalf Of David-Sarah Hopwood
> Sent: Thursday, November 06, 2008 5:11 PM
> To: es-discuss at mozilla.org; es3.x-discuss at mozilla.org
> Subject: Re: Draft of Function.prototype.bind.
> Brendan Eich wrote:
> > On Nov 4, 2008, at 10:52 AM, David-Sarah Hopwood wrote:
> >> Brendan Eich wrote:
> >>> We'll make regexps non-callable in a future release whose numbering
> >>> allows us to break compatibility for all the users who may be
> relying on
> >>> this JS extension.
> >> What's wrong with that release being the one that first supports
> >> (so that in ES3.1, native objects are callable iff they are
> > Maybe. Let's finish ES3.1 first.
> You can always remove callable regexps before ES3.1; my point was that
> at least one technically incompatible release will be needed in order
> to support ES3.1.
> >> There will be other minor incompatibilities that are required by
> >> so it seems as though that release will have to be one "whose
> >> allows [you] to break compatibility".
> > Where are the ES3.1 incompatibilities vs. ES3 summarized?
> Annexes D and E of the Kona draft.
> Also, any addition of a property (of one of the built-in objects) or a
> global (such as 'JSON') is a theoretical incompatibility, since it
> have been possible to write code that depended on the non-existance of
> that property or global.
> David-Sarah Hopwood
> Es3.x-discuss mailing list
> Es3.x-discuss at mozilla.org
More information about the Es-discuss