IG stuff

After playing a bit with the inspections:

  • Performance issues->String concatenation in loop

Ummh, it complains about any string concatination in loops, eq.:
Collection]]> test=...;
for(String s : test) {
System.out.println("Entry: "+s);
Shouldn't this just check for adding something to an variable/field
outside the loop?

  • Java5 issues->Raw use of parameterized class

also complains about instanceof '(o instanceof Class)'
But the spec does not allow an parameterized cast.

0
3 comments
Avatar
Permanently deleted user

Hi Sven,

If you add JIRA entries the chance it higher that the bugs are solved.

Tom

0
Avatar
Permanently deleted user

If you add JIRA entries the chance it higher that the bugs are solved.


Yep, I know. But placing problems/bugs first on the list usually results
in some discussion.
The "Raw use of parameterized type" problem also refers to some other
fields. Eq. when casting, the warning/error is also not necessary, I think.

0
Avatar
Permanently deleted user

Sven Steiniger wrote:

  • Java5 issues->Raw use of parameterized class

also complains about instanceof '(o instanceof Class)'
But the spec does not allow an parameterized cast.


Nope, the correct way is "o instanceof Class<?>"

0

Please sign in to leave a comment.