On Nov 2, 2011, at 4:51 PM, Nebojša Ćirić wrote:
> My main concern at the moment is ES5. It seems that best practice is to
> declare [[Extensible]]:true, which would in turn avoid conflicts with
> pre-existing globals and let developers append new functionality to
> Globalization. We can deal with modules in the future revisions if necessary.
That's a fine approach if you really are making a spec that adds onto ES5.
Depends on timing.
/be
>
> 02. новембар 2011. 16.20, Brendan Eich <bren...@mozilla.com> је написао/ла:
> On Nov 2, 2011, at 4:09 PM, Allen Wirfs-Brock wrote:
>
> > Ideally, the globalization support would manifest as a global (or
> > properties on an existing global) in ES5 implementations and as a module in
> > ES.next. Do we know how to actually make that work?
>
> What we did talk about was exposing the system loader to unversioned script
> through an API, say Object.System. Then you could Object.System.load("@g11n"
> ...) and get stuff done. The built-ins should not require a callback
>
> /be
>
>
>
>
> --
> Nebojša Ćirić
> _______________________________________________
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
