Let eclipse warn about a semicolon after an if statement and string == string?

[foobar.fighter]

Is there any way eclipse can warn me about statements like

if (foo.equals(bar));
{
 // this will always be executed

}

or

if (username == "Foo bar fighter")  // probably never true

?

[foobar.fighter]

Is my question stupid or unclear or impossible?

[Steve11235]

Eclipse preferences, somewhere in Java.compiler, lets you set up warnings, and you can also specify formatter settings that will force your code into a style that exposes those sorts of errors. For example, you might be able to expose the first one by requiring all if statements to use {}.

Having said that, it won't stop you from doing things that are strange but valid. The second falls in that category, afaik.

If it was easy, no one would pay you to do it ;-)

[Eranga]

Since those things are errors, why you just want to see them as warnings. I think Eclipse clearly state those things as errors. Seems to me this is annoying thing our thread starter wants to do.

[Steve11235]

I've never tried the first one, but I *think* it might be a valid statement. The second is a fragment, but the idea is valid.

I think ff wants the compiler to warn him/her about slip ups that end up compiling but that don't make sense. That's why I said it's not easy, the compiler can't do all the work for us...

[foobar.fighter]

I've never tried the first one, but I *think* it might be a valid statement. The second is a fragment, but the idea is valid.

I think ff wants the compiler to warn him/her about slip ups that end up compiling but that don't make sense. That's why I said it's not easy, the compiler can't do all the work for us...

Yes, this is exactly my point; both compile but don't make sense.

I thought there might be a simple plugin which allows me to write some code which checks my source code; I could just simply match some kind of /if.*;/ regular expression to find the first one.