commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LANG-842) Lack of consistency in comparaison api
Date Tue, 15 Oct 2013 03:40:42 GMT

    [ https://issues.apache.org/jira/browse/LANG-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794845#comment-13794845
] 

Henri Yandell commented on LANG-842:
------------------------------------

I think we can ignore comparison with the time.* API. We've long favoured JODA Time to using
the central Java classes and if we get a new date/time API in Java 8, I can see Lang 4.0 dropping
the time.* package and porting whichever functions are considered valuable on top of the new
API.

> Lack of consistency in comparaison api
> --------------------------------------
>
>                 Key: LANG-842
>                 URL: https://issues.apache.org/jira/browse/LANG-842
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.*, lang.time.*
>    Affects Versions: 3.2
>            Reporter: Pier-Luc Caron St-Pierre
>            Priority: Trivial
>
> The comparaison api is lacking of consistency with null.
> Few instances : 
> org.apache.commons.lang3.StringUtils#equals returns false if one of the parameter is
null.
> org.apache.commons.lang3.ObjectUtils#equals returns false if one of the parameter is
null.
> org.apache.commons.lang3.time.DateUtils#truncatedCompareTo throws IllegalArgumentException
if one of the parameter is null
> org.apache.commons.lang3.time.DateUtils#isSameInstant throws IllegalArgumentException
if one of the parameter is null
> I do not have any suggestion to fix that problem because any solution would break backward
compatibility.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message