[gwt-contrib] Re: JSNI signature shortcuts

2009-02-13 Thread Lex Spoon
+1 to the whole idea. Also, for the reasons already given, I agree that ::method looks better than this::method, which looks better than self::method. I am not sure it's worth the spec weight to have a lot of variants in the syntax. The most important thing is to allow * in place of an entire m

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Matthew Mastracci
I filed issue 3358 to track this feature: http://code.google.com/p/google-web-toolkit/issues/detail?id=3358 On 12-Feb-09, at 2:23 PM, Ray Cromwell wrote: > > I prefer :: also, but if you need another reserved Java keyword, you > could use 'class', e.g. class::foo > > -Ray > > > On Thu, Feb 12,

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Ray Cromwell
I prefer :: also, but if you need another reserved Java keyword, you could use 'class', e.g. class::foo -Ray On Thu, Feb 12, 2009 at 1:21 PM, John Tamplin wrote: > On Thu, Feb 12, 2009 at 4:17 PM, Scott Blum wrote: >> >> Just use 'this' instead of 'self'. 'this' is a Java keyword so it can't

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread John Tamplin
On Thu, Feb 12, 2009 at 4:17 PM, Scott Blum wrote: > Just use 'this' instead of 'self'. 'this' is a Java keyword so it can't be > a classname. Seems awkward to use this to refer to a class rather than an instance -- I still prefer just :: to mean the same class. -- John A. Tamplin Software E

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Scott Blum
Just use 'this' instead of 'self'. 'this' is a Java keyword so it can't be a classname. On Thu, Feb 12, 2009 at 3:12 PM, John Tamplin wrote: > I think JSNI references should honor imports and the normal name resolution > process -- that would eliminate much of the wordiness. > > Regarding the s

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Matthew Mastracci
On 12-Feb-09, at 1:12 PM, John Tamplin wrote: > I think JSNI references should honor imports and the normal name > resolution process -- that would eliminate much of the wordiness. > > Regarding the syntax, I would prefer ::xxx to self::xxx, being more > concise and avoiding ambiguity if a cl

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread John Tamplin
I think JSNI references should honor imports and the normal name resolution process -- that would eliminate much of the wordiness. Regarding the syntax, I would prefer ::xxx to self::xxx, being more concise and avoiding ambiguity if a class named "self" exists. -- John A. Tamplin Software Engine

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Bruce Johnson
+1 to the concept; need more time to think through the specifics, but it's needed On Thu, Feb 12, 2009 at 3:00 PM, Matthew Mastracci wrote: > > Hey all, > > I'd like to propose a feature for a future GWT release: JSNI signature > shortcuts. > > == > > JSNI references are an ad

[gwt-contrib] Re: JSNI signature shortcuts

2009-02-12 Thread Scott Blum
My thoughts are... +1! --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---