Re: Gee Functional iterators

On Wed, Jul 14, 2010 at 9:01 AM, Maciej Piechotka <uzytkownik2 gmail com> wrote:
> Solution:
> a) Add is_pointing or similar property and check if the iterator is
> pointing somewhere then perform is_next (breaks API/ABI and produces
> horrible code)
> b) Point always on element, past-the-end or before-the-beginning like in
> C++/STL.
> c) Just return a new iterator in skip operations.
> d) Add get_next/lookahead methods
> 2. The remove method makes no sense for the many of iterators now. For

How would you feel about a new read-only iterator type? I think if we
wrote one specifically designed to be used by our functional library,
it need not even leak out into the rest of libgee at all. Having our
own iterator would also let us add is_pointing and whatever else we
needed. Also, I like the idea of not being able to mutate a collection
while in the process of doing "functional" iteration over it.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]