+1 Freeland. You may then also like the planned "private goto", which goes somewhere but it doesn't tell you where it's gone.
On Tuesday, November 17, 2009, Freeland Abbott <fabb...@google.com> wrote: > Personally, I'm holding out for "transient goto"... imagine being able to > leap to another chunk of code, and then back again when it finishes! > > On Tue, Nov 17, 2009 at 5:27 PM, Bruce Johnson <br...@google.com> wrote: > I'm especially excited about "goto"! Think of how powerful and flexible that > will be! > > > On Tue, Nov 17, 2009 at 3:13 PM, Daniel Rice (דניאל רייס) <r...@google.com> > wrote: >> // "future reserved words" >> "abstract", "int", "short", "boolean", "interface", "static", "byte", >> "long", "char", "final", "native", "synchronized", "float", "package", >> "throws", "goto", "private", "transient", "implements", "protected", >> "volatile", "double", "public", > > What a future it will be... > > Dan > > On Tue, Nov 17, 2009 at 3:11 PM, Freeland Abbott <fabb...@google.com> wrote: >> I don't promise this is exhaustive, but it catches up to the mozilla and IE >> references, plus uneval from issue 3965. (Which wasn't on the mozilla >> pages, despite being reserved there, so I'm in fact almost sure this >> isn't exhaustive...) >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
