> This can be fixed of course; make unhandled checked exceptions a warning,
> but instead of using @SuppressWarnings, create a new annotation that accepts
> a list of class types:
>
> @SuppressChecked(UnsupportedEncodingException.class)
> public void whatever() {
> .... something that throws UnsupportedEncodingException for no good
> reason ...
Right, that approach would also fix up the nasty guesswork of strings
inside SuppressWarnings() which was a mistake not to standardize (the
spec mentions just one or two, the JDK supports 7-8, Eclipse supports
others etc.).
I struggle to see the pro-checked-exception people's argument against
such a step towards greater leniency, not a single unit-test would
fail. Think about it, it would fall naturally in under the -Xlint
argument for javac.
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
