"default" keyword inconsistency: *before* default methods in interfaces, *after* default attributes in annotations

[Ricky Clarkson]

It was as you suggest some months back.  The change was intended to make it
a modifier (like abstract, static, private etc.) and be in the same
position as the other modifiers.


On Fri, Feb 8, 2013 at 11:42 AM, Rogerio Liesenfeld
<rliesenfeld at gmail.com>wrote:

> Hello,
>
> In lambda_b75, I noticed that the “default” keyword is being used
> *before* the method name in default method declarations inside
> interfaces.
> This contradicts current usage of the same keyword in annotation
> types, where it must appear *after* the method name. This is since
> Java 5.
>
> For example, consider the following annotation type declaration:
>
> public @interface RequestForEnhancement {
>     int    id();
>     String engineer() default "[unassigned]";
> }
>
> Attributes like “engineer” above are similar to default methods such as:
>
> public interface RequestForEnhancement {
>     int    id();
>     default String engineer(){ return "[unassigned]"; }
> }
>
> It would be more consistent with “default” after the method.
>
>