Re: [Boost-users] chaining ouput iterator to input iterator

-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of Nat Linden Sent: 09 July 2012 13:24 To: boost-users@lists.boost.org Subject: Re: [Boost-users] chaining ouput iterator to input iterator

On Sun, Jul 8, 2012 at 5:33 PM, MM wrote:

...

...

-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of Nathan Ridge Sent: 08 July 2012 15:33 To: Boost Mailing List Subject: Re: [Boost-users] chaining ouput iterator to input iterator

your options are ... 2) use a Boost.Context-based solution as I mentioned before.

...

Boost.Coroutine? Is that in boost vault?

Heh. There is a Boost.Coroutine in the Vault, but you're better advised to use the new Boost.Coroutine just coming up for review this week (I believe).

IMO, either would be better than directly using Boost.Context. Context is a low-level library intended for use by application-level libraries such as Coroutine. It's just that any application-level library based on user-space context switching necessarily deals with the same platform-dependent issues; Oliver Kowalke has very usefully abstracted those out as Context.

Now Oliver has presented us with a reimplementation of the original Boost.Coroutine prototype (in the Vault), based on his Context library. If you're willing, it would be very timely to add your opinion to the review about to be announced.

Presumably the doc is in the boost vault. I'll take a look Frankly, the coroutine seems very unnatural as I am accustomed to the separation of concerns, and the mechanism of of function call, and so on... I was also wondering if some lazy function from phoenix could help with this, or really a boost::transform_iterator could do it somehow MM