[
https://issues.apache.org/jira/browse/COLLECTIONS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649751#comment-13649751
]
Thomas Neidhart commented on COLLECTIONS-442:
---------------------------------------------
Thanks for the feedback!
I like both styles, and as you say, they can be useful under different
circumstances.
At collections, we already have a class IteratorUtils, where all the static
functions should go (some of them are already there) imho.
Tbh I am not such a big fan of these *Utils, and their quite expressive method
names, but thats the common style of collections, so we should better stick to
it to be consistent.
For the method chaining style: I will re-work it further to mimic the API of
Iter, we should just use the existing classes in collections to avoid
duplication of code / effort.
Regarding more additions from jena, I will create sub-tasks for each addition
to better keep track of the things that have been added. The PeekingIterator is
definitely useful.
> A set of enhanced iterator classes donated by the Apache Jena project
> ---------------------------------------------------------------------
>
> Key: COLLECTIONS-442
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-442
> Project: Commons Collections
> Issue Type: Improvement
> Components: Iterator
> Reporter: Claude Warren
> Fix For: 4.0
>
> Attachments: COLLECTIONS-442.tar.gz, FluentIterator.java, iter-src.zip
>
>
> A set of templated (Generic) iterators that add filtering, mapping, and
> conversion to set or list collections. Tests included.
--
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
