commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LANG-366) add MultiFormat
Date Sat, 02 Feb 2008 19:38:08 GMT

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

Matt Benson commented on LANG-366:
----------------------------------

:|  Here we are again and again I am forced to disagree with you, Niall.  On your second issue,
regarding consuming all the input, again I defer to the Format API.  parseObject(String, ParsePosition)
is specifically declared to consume only as much of the incoming String as necessary, so forcing
all input to be consumed would defeat the goals of the API at least in part.  This is why
ParsePosition has an updatable index; otherwise returning an Object vs. throwing an Exception
would be sufficient behavior.  On the first issue I don't exactly have a problem except for
the fact that I can't see how it would be compatible with the part of my EMF code in which
it's used (and which dictated the creation of MultiFormat).  We can defer that discussion
until we reach consensus on the EMF issue, but perhaps a TypeKeyedFormat or some such might
be an option.

Thanks,
Matt

> add MultiFormat
> ---------------
>
>                 Key: LANG-366
>                 URL: https://issues.apache.org/jira/browse/LANG-366
>             Project: Commons Lang
>          Issue Type: New Feature
>            Reporter: Matt Benson
>             Fix For: 2.4
>
>         Attachments: multiFormat.patch.txt, MultiFormat2.java
>
>
> this started as a part of LANG-362.  That PR depends on this one.

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


Mime
View raw message