[jira] Commented: (CONFIGURATION-422) Configuration.getInt() should define its accepted inputs, and should also accept octal

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CONFIGURATION-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878933#action_12878933 ] 

Sebb commented on CONFIGURATION-422:
------------------------------------

0x seems reasonable.

However allowing a 0-prefix to mean octal could break some existing code that relies on leading zeros being ignored.

> Configuration.getInt() should define its accepted inputs, and should also accept octal
> --------------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-422
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-422
>             Project: Commons Configuration
>          Issue Type: Improvement
>          Components: Type conversion
>            Reporter: david cogen
>            Priority: Minor
>
> I can find no information about the format of the string that Configuration.getInt(String) accepts. I have determined by experimentation and examining the source that it accepts decimal integers, and hex integers if preceeded by "0x". This should be explained.
> Also, it is customary for functions which accept decimal and hex to also accept octal. A string with leading "0" should be parsed as octal.
> This should apply to getByte(), getShort(), and getLong() as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.