Re: Java language and library suggestions

From:

Tomas Mikula <tomas.mikula@gmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Sun, 19 Jul 2009 06:57:21 -0700 (PDT)

Message-ID:

<d8caccc0-1484-4c2c-8d3a-734f2a42590a@v20g2000yqm.googlegroups.com>

Thank everyone for the opinions. I thought that @safe was something
everyone would like to have. But I see it didn't get much acceptance.
Still none of the arguments presented so far has convinced me that
it's a bad idea to have this in the language. But I would be happy
with more powerful annotations that would allow to change the code
being annotated at compile time.

On Jul 19, 12:57 pm, Tom Anderson <t...@urchin.earth.li> wrote:

On Sat, 18 Jul 2009, Tomas Mikula wrote:

Consider the example:

int i;
try {
i = Integer.parseInt(valid_int_string);
} catch(NumberFormatException e) {
throw new AssertionError(e);
}

What you say means that I should not throw AssertionError, because in
the future the code could really throw the NumberFormatException. But
if it does, I still want to get the AssertionError, because
continueing without the correct value in i does not have any sense.

Since NumberFormatException is a runtime exception, this is a bad example=

..

My mistake.

Tomas