Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sun, 12 Jan 2014 10:10:51 +0000 (UTC)
From: "Benedikt Ritter (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12609401.1348756830712.83484.1389521451852@arcas>
In-Reply-To: <JIRA.12609401.1348756830712@arcas>
References: <JIRA.12609401.1348756830712@arcas>
Subject: [jira] [Updated] (LANG-834) Validate: add inclusiveBetween(long
 start, long end, long value) methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LANG-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedikt Ritter updated LANG-834:
---------------------------------

    Fix Version/s: 3.3

> Validate: add inclusiveBetween(long start, long end, long value) methods
> ------------------------------------------------------------------------
>
>                 Key: LANG-834
>                 URL: https://issues.apache.org/jira/browse/LANG-834
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.*
>    Affects Versions: 3.1
>            Reporter: Sebb
>             Fix For: 3.3, Review Patch
>
>         Attachments: LANG-834.patch
>
>
> Validate.inclusiveBetween() is often going to be used with primitives, so it might make sense to add 
> inclusiveBetween(long start, long end, long value)
> and
> inclusiveBetween(long start, long end, long value, String message)
> This would avoid the overhead of using boxing and compareTo() for the primitive number types.
> Note: I tried adding
> inclusiveBetween(long start, long end, long value, String message, Object ... values)
> but that causes the compiler to complain about ambiguous methods.
> However, that's unlikely to be needed much.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)