Synopsis: | These rules deal with different problems that can occur with manipulation of the class String or StringBuffer. |
Description: |
These rules deal with different problems that can occur with manipulation of the class String or StringBuffer. |
Name | Checked | Synopsis |
---|---|---|
StringandStringBuffer1 | ![]() |
Don't use duplicate String literals; use constants instead |
StringandStringBuffer2 | ![]() |
Avoid instantiating String objects; this is usually unnecessary |
StringandStringBuffer3 | ![]() |
Avoid calling toString() on String objects; this is unnecessary |
StringandStringBuffer4 | ![]() |
Avoid concatenating nonliterals in a StringBuffer constructor or append() |
StringandStringBuffer5 | ![]() |
Using equalsIgnoreCase() is cleaner than using toUpperCase/toLowerCase().equals() |
StringandStringBuffer6 | ![]() |
This is an inefficient use of StringBuffer.toString; call StringBuffer.length instead |
StringandStringBuffer7 | ![]() |
Avoid appending characters as strings in StringBuffer.append |
StringandStringBuffer8 | ![]() |
Combine StringBuffer.append calls, if possible |
StringandStringBuffer9 | ![]() |
String.indexOf(char) is faster than String.indexOf(String) |
StringandStringBuffer10 | ![]() |
String.trim().length()==0 is an inefficient way to validate an empty String |
StringandStringBuffer11 | ![]() |
Initialize objects of StringBuffer with a proper size |
StringandStringBuffer12 | ![]() |
No need to call String.valueOf to append to a string |
StringandStringBuffer13 | ![]() |
Do not instantiate a StringBuffer with a char |
StringandStringBuffer14 | ![]() |
Use equals() to compare String objects |