Coding guidelines adjusted

[Cantor, Scott]

On 4/26/13 2:43 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>I will do some additional research into the nullability annotations and
>propose further changes if warranted.

I found some Java 8 information here:

http://docs.oracle.com/javase/tutorial/java/annotations/type_annotations.ht
ml

As you'll see, they have not added nullability annotations to the system.
Rather, they enhanced where annotations can live, and made the system more
pluggable for others to add code checking tools into.

They point to one at the University of Washington:

http://types.cs.washington.edu/checker-framework/

That would be appropriate given the history of the project, so I had to
laugh. Anyway, it uses annotations that are not in javax.annotation, of
course, and also spells @Nonnull with camel case.

I don't think it is likely that we're going to see Nullable added to Java
soon if at all, so I believe that we should eventually migrate these
annotations to a different set that fits *some* tool. Eclipse's would seem
a logical choice to me. In the meantime, we can proceed as we have been.

-- Scott