obsoleting the "new" keyword
erik.arvidsson at gmail.com
Wed Jan 14 09:54:33 PST 2009
The *new* keyword makes thing more readable and I agree with both Kris
and Alex here that any class syntax we come up with should use *new*
to look and feel like "classes" as used today in ES.
I'm fine with making this optional since it would allow us to strip
"new " from the files we send over the wire ;-)
2009/1/14 Alex Russell <alex at dojotoolkit.org>:
> I think I'm w/ Kris on this:
> I'd be in favor of the "new" protocol being exposed in a programmatic way, e.g.:
> var instance = someClassName.new();
> On Jan 14, 2009, at 9:21 AM, Kris Zyp wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> I certainly hope not. A fundamental requirement of class sugar should
>> be that it properly leverages "new".
>> Peter Michaux wrote:
>>> been lamented. One of the key "looks" was the "new" keyword. Many
>>> people don't like the use of the "new" keyword. Although "new" is
>>> here to stay, could we obsolete it when using a class sugar?
> Es-discuss mailing list
> Es-discuss at mozilla.org
More information about the Es-discuss