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.
02. новембар 2011. 16.20, Brendan Eich <[email protected]> је написао/ла: > 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 [email protected] https://mail.mozilla.org/listinfo/es-discuss
