[
https://issues.apache.org/jira/browse/CODEC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083402#comment-13083402
]
Gary D. Gregory commented on CODEC-125:
---------------------------------------
Hi Matthew, Sebb, and all:
The next release will already be a big bump to *2.0* (from 1.5.) The trunk code
is already on Java 5 but generics have not been implemented. Implementing
generics will probably change some of class/API layout due to some encoders
supporting multiple input/output types.
The trunk also has removed deprecated methods, which means binary
incompatibilities, which means the package name and POM should change.
*Right, Seeb? Others?*
This would also mean that codec2 would not be a drop in for codec1 but that
both could live side by side.
If we set the API to {{CharSequence encode(Set<CharSequence>)}} or {{String
encode(Set<String>)}}, doing a toString on a HashSet will yield a usable String
in a similar vein as trunk now. For example, for a Set of Strings {{"a"}},
{{"b"}} and {{"c"}}, {{HashSet.toString()}} returns {{"[a, b, c]"}} which no
worse than {{"a|b|c"}} IMO.
So we can have our cake and eat it too.
> Implement a Beider-Morse phonetic matching codec
> ------------------------------------------------
>
> Key: CODEC-125
> URL: https://issues.apache.org/jira/browse/CODEC-125
> Project: Commons Codec
> Issue Type: New Feature
> Reporter: Matthew Pocock
> Priority: Minor
> Attachments: Rule$4$1-All_Objects.html, acz.patch, bm-gg.diff,
> bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch, bmpm.patch,
> bmpm.patch, bmpm.patch, comparator.patch, fightingMemoryChurn.patch,
> fightingMemoryChurn.patch, fixmeInvariant.patch, handleH.patch,
> majorFix.patch, performanceAndBugs.patch, testAllChars-mem-profile.html,
> testEncodeGna.patch
>
>
> I have implemented Beider Morse Phonetic Matching as a codec against the
> commons-codec svn trunk. I would like to contribute this to commons-codec.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira