Re: [boost] Determining interest in combining_iterator

2003-03-29 Thread Thomas Becker
<[EMAIL PROTECTED]> wrote: > FWIW, I've extended my pair iterator to be a tuple > iterator for > input/forward/bidirectional/random-access iterator > categories, which was > relatively painless. I will boostify it, add output > iterator support back in, > and test it with VC7.1 as well as g++ 3.2.2

Re: [boost] Determining interest in combining_iterator

2003-03-27 Thread Thomas Becker
--- Anthony Williams <[EMAIL PROTECTED]> wrote: > Basically, I think we have two contradictory > scenarios. IIUC, the situations > you have encountered are where you have a set of > values in different > containers that needed to be combined into a single > value, in which case it > makes sense t

Re: [boost] Determining interest in combining_iterator

2003-03-26 Thread Thomas Becker
> On 26 Mar 2003, Anthony Williams wrote: > > It strikes me that if you dereference n iterators, > you have n values, and the > most natural way to store them is a tuple. --- Douglas Paul Gregor <[EMAIL PROTECTED]> wrote: > I would agree if tuples and argument passing were > more closely linked, >

Re: [boost] Determining interest in combining_iterator

2003-03-25 Thread David Abrahams
Thomas Becker <[EMAIL PROTECTED]> writes: > Thanks for your comments on the combining iterator. > >> David Abrahams wrote: It's a wonderful idea, Thomas! >> You might look at the Boost sandbox; Jeremy Siek, Thomas Witt and I >> are trying to finalize the work in the boost/iterator and >> libs/iter

Re: [boost] Determining interest in combining_iterator

2003-03-25 Thread Thomas Becker
Thanks for your comments on the combining iterator. > David Abrahams wrote: > It's a wonderful idea, Thomas! > > You might look at the Boost sandbox; Jeremy Siek, > Thomas Witt and I > are trying to finalize the work in the > boost/iterator and > libs/iterator directories to replace the current

RE: [boost] Determining interest in combining_iterator

2003-03-24 Thread Paul A. Bristow
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Thomas Becker > Sent: Monday, March 24, 2003 7:50 AM > To: [EMAIL PROTECTED] > Subject: [boost] Determining interest in combining_iterator > > This email is to determin

Re: [boost] Determining interest in combining_iterator

2003-03-24 Thread Douglas Paul Gregor
> The combining iterator is another iterator adaptor. It > holds a boost::tuple of iterators. Moving the > combining iterator in any way causes all member > iterators of the tuple to move in parallel. Upon > dereferencing the combining iterator, the dereferenced > values of the member iterators are

Re: [boost] Determining interest in combining_iterator

2003-03-24 Thread David Abrahams
Thomas Becker <[EMAIL PROTECTED]> writes: > I recently noticed that the ready-to-use boost now provide almost > everything that we use, with the exception of the combining > iterator. But this is a very important one for us, hence the > proposed submission. > > Please comment. It's a wonderful i

[boost] Determining interest in combining_iterator

2003-03-24 Thread Thomas Becker
This email is to determine possible interest in a submission to boost: the combining iterator. Short Description = The combining iterator is another iterator adaptor. It holds a boost::tuple of iterators. Moving the combining iterator in any way causes all member iterators of the t