yc, There's no GWT-specific reason to declare the interface abstract. The GWT compiler, just like the Java compiler, will discard the abstract qualifier.
On Thu, Jan 7, 2010 at 8:44 PM, yc <ycx4...@gmail.com> wrote:
> Hello,
>
> If you have reviewed the Contacts example in the GWT tutorial, the
> "Presenter" interface is defined as the following in the example:
>
> public abstract interface Presenter {
> public abstract void go(final HasWidgets container);
> }
>
> Here is what section 9.1.1 in JLC (2nd edition) has to say:
> --- quote ---
> 9.1.1.1 abstract Interfaces
> Every interface is implicitly abstract. This modifier is obsolete and
> should not be used in new programs.
> --- end of quote ---
>
> Am I missing something here that the "abstract" modifier is being used
> in this example to trigger some JavaScript compiler optimization
> techniques? I would have just ignored the modifier if this were a
> regular Java program but this one gives me sweat since it is intended
> to be compiled into JavaScript source...so what I am missing?
>
> yc
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
