[LANG-1252] NumberUtils.isNumber and NumberUtils.createNumber resolve inconsistently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4
• Fix Version/s: 3.5
• Component/s: lang.math.*
• Assignee: Rob Tompkins
• Reporter: Rob Tompkins
• Created: 28/Jul/16 11:33
• Updated: 19/Oct/16 07:01
• Resolved: 11/Sep/16 20:36

Description

In considering the issues LANG-1060, LANG-1040, LANG-1038, and LANG-992, it seems that there are times when NumberUtils.isNumber resolves to false while NumberUtils.createNumber, given the same input, does not throw an exception, returning a valid java.lang.Number. This inconsistency should be resolved either by making isNumber more lenient or createNumber more stringent.

Issue Links

• is related to: LANG-992 NumberUtils#isNumber() returns false for "0.0", "0.4790", et al
• is related to: LANG-1038 NumberUtils#isNumber() returns false for "+2" and true for "-2"
• is related to: LANG-1040 Javadoc for NumberUtils.isNumber() are not clear enough
• relates to: LANG-992 NumberUtils#isNumber() returns false for "0.0", "0.4790", et al
• relates to: LANG-1038 NumberUtils#isNumber() returns false for "+2" and true for "-2"
• relates to: LANG-1040 Javadoc for NumberUtils.isNumber() are not clear enough
• relates to: LANG-1060 NumberUtils.isNumber assumes number starting with Zero is octal
• links to: GitHub Pull Request #186