Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Why not String compare? Date: Fri, 26 Aug 2016 18:49:22 +0200 Lines: 14 Message-ID: References: <33463070-424f-4fb0-956b-2849f1a400eb@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net brrwRxwmzpwVBwudQ84ikAvy4ZgU6NnmNEz3LUH0JnzYuIsJs= Cancel-Lock: sha1:e6ab2BZ77MNAnZeaKOMsaDzqF74= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 In-Reply-To: <33463070-424f-4fb0-956b-2849f1a400eb@googlegroups.com> Xref: csiph.com comp.lang.java.programmer:35467 On 26.08.2016 18:00, Eric Douglas wrote: > This seems odd, the String class returns false if you pass a null > into equals(), but throws NPE if you pass null into compareTo(). The > Javadoc on it's compareTo() doesn't mention nulls much less NPE. The > Javadoc on Comparator mentions it'll return NPE by default for a > null, but any time I write a custom Comparator I return 1 for > compareTo() if argument is null. http://docs.oracle.com/javase/8/docs/api/java/lang/Comparable.html#compareTo-T- -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/