Yes, there is a best practice. Contrary to what the other answers are saying, there is an expected standard, not just a most popular behavior. The correct answer is given in the MSDN documentation for IComparable<T>.CompareTo and IComparable.CompareTo: By definition, any object compares greater than null, and two null references compare equal to each other. … Read more
Both internally does the same thing. Compare Ticks and return result. public int CompareTo(TimeSpan value) { long t = value._ticks; if (_ticks > t) return 1; if (_ticks < t) return -1; return 0; } public static bool operator <(TimeSpan t1, TimeSpan t2) { return t1._ticks < t2._ticks; } The only reason could be the … Read more
see this: From http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#source Area: API: Utilities Synopsis: Updated sort behavior for Arrays and Collections may throw an IllegalArgumentException Description: The sorting algorithm used by java.util.Arrays.sort and (indirectly) by java.util.Collections.sort has been replaced. The new sort implementation may throw an IllegalArgumentException if it detects a Comparable that violates the Comparable contract. The previous implementation silently … Read more
The implementation of Integer.compare does not use subtraction, as this could cause an overflow in case you’re comparing an integer that is close to Integer.MIN_VALUE with another that is close to Integer.MAX_VALUE. This overflow cannot happen in case of Byte.compare, as there the byte values are implicitely converted to integers before x-y is calculated. (see … Read more
For performance, it usually best to make the code as simple and clear as possible and this will often perform well (as the JIT will optimise this code best). In your case, the simplest examples are also likely to be the fastest. I would do either int cmp = a > b ? +1 : … Read more
For consistency I guess… when you see an enum type, you know for a fact that its natural ordering is the order in which the constants are declared. To workaround this, you can easily create your own Comparator<MyEnum> and use it whenever you need a different ordering: enum MyEnum { DOG(“woof”), CAT(“meow”); String sound; MyEnum(String … Read more
A difference is that “foo”.equals((String)null) returns false while “foo”.compareTo((String)null) == 0 throws a NullPointerException. So they are not always interchangeable even for Strings.
The answer is in the JavaDoc of the equals() method: Unlike compareTo, this method considers two BigDecimal objects equal only if they are equal in value and scale (thus 2.0 is not equal to 2.00 when compared by this method). In other words: equals() checks if the BigDecimal objects are exactly the same in every … Read more
You can simply use Apache Commons Lang: result = ObjectUtils.compare(firstComparable, secondComparable)