RE: Java - Backwards - Second Draft |
||
 Ret. Gen D-Cypell Its not the fact that it is quicker that makes "literal".equals(str) a smart thing to do. The real reason is that it protects against null pointer exceptions. If str is null... str.equals("literal") will throw an NPE because you cant call .equals on null. If you put the literal first it obviously can never be null. In this case it doesnt matter too much because null is checked for anyway. On 2005-02-26 02:15:52, flamebalrog wrote >On 2005-02-24 20:18:01, SAJChurchey wrote >> >>public static String Backwards(String str){ >> if(str == null || str.trim().equals("")) >> return ""; >> str = str.trim(); >> StringBuffer newString = new StringBuffer(str); >> return newString.reverse().toString(); >>} >> > >A not-null-and-not-empty-and-not-space-only String (one that will be reversed) is trimmed twice with your code (1st to test it, 2nd after the test). You could avoid it. > >Also, I think ' "literalString".equals(expression) ' is faster than ' expression.equals("literalString") '...can anyone confirm ? Replies:
|
||
| CyberArmy::Forum v0.6 Generated In 0.02289 seconds |
2005-02-15 17:19:31
2006-01-03 05:04:05
2005-03-21 03:08:22
2005-03-14 19:01:39
2005-03-24 22:41:05
2005-02-17 20:09:14
2005-02-15 20:12:52