You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Charles Honton (JIRA)" <ji...@apache.org> on 2012/09/27 07:15:08 UTC

[jira] [Resolved] (LANG-829) FastDateParser could use Calendar.getDisplayNames for all text fields

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

Charles Honton resolved LANG-829.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2

URL: http://svn.apache.org/viewvc?view=revision&revision=1390839

Modified:
 commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3/time/FastDateParser.java

                
> FastDateParser could use Calendar.getDisplayNames for all text fields
> ---------------------------------------------------------------------
>
>                 Key: LANG-829
>                 URL: https://issues.apache.org/jira/browse/LANG-829
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.time.*
>            Reporter: Sebb
>            Assignee: Charles Honton
>            Priority: Minor
>             Fix For: 3.2
>
>
> FastDateParser could use Calendar.getDisplayNames for all text fields.
> This returns a map of names to indexes, which would be easier to search - no need to sort the symbols, and no need for the KeyValue instances.
> Also, the nameValues entries are only used by the TextStrategy, so could be saved in the instance.
> Overall this should reduce memory and be quicker.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira