I'd be inclined to believe that this interface started life as an abstract class, and at some point the developer decided that it could be an interface instead. Thus the declaration was changed but the abstract modifiers were not removed.
I think that there were no more nefarious intentions than that.
-jason
On Jan 7, 2010, at 6:44 PM, yc 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.
> 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.
