"David Abrahams" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Alisdair Meredith <[EMAIL PROTECTED]> writes: > > > This is clear when we look at algorithms that take a range for input and > > an output iterator, eg transform. Where I see a range and an iterator, > > your library tries to see two containers. I'm not entirely convinced > > this is the way to go. > > >From working with the MPL, which does almost everything in terms of > sequences, I can say it is occasionally inconvenient to come up with > two sequences for an algorithm like the 2-sequence form of > transform. If you just have an iterator into the 2nd sequence, it > may be hard to come up with another one to mark the end. That's > especially true in the runtime world, where single-pass iterators are > possible (think istream_iterator).
I guess you wouldn't have to come up with another iterrator, you could just use a dummy one since the end is not used. -Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
