Le 07/03/14 15:32, Thaler Benedek a écrit :

[snip]

...

What about adding some comments to the code? Hi Vicente,

I've added some comments, maybe it's clearer now. Let me emphasize, it's only a demo, e.g: the way of how segment::run(...) works wouldn't play nicely in a multithreaded environment, it will be changed later.

Don't worry, it is ok for a first step. Vicente

Le 13/03/14 23:06, Thaler Benedek a écrit :

...

I'm interested in the Boost.Pipelines proposal of GSoC 2014. [snip]

My proposal of proposal can be found online: [0]. Please take a look and notify me if you miss something or if you have any general comment.

Hi, Your proposal is almost perfect. You have been able to implement a POC and generate the documentation using the Boost environment tools. You seem to master the problem domain. Concerning the project proposal, I would like to see the following points more elaborated: * Why do you think that value semantic would be better? * How would you specify the queue as a policy parameter? * Do you plan to make the thread pool configurable? * Do you plan to port it to C++98 compilers? * What your performance tests will measure? Do you plan to compare different implementations? Value-semantics versus shared semantics? Different queues? Different thread pools? Concerning the millstones, I would prefer a week based schedule and that as far as possible each iteration includes something adding value with the code the tests and the documentation. Maybe enumerating the use cases by priority would help. * 1-1 transformations * 1-N transformations * N-M transformations * parallel segments * make use of thread pools * queue configuration On each of these use cases maybe you could list the classes that you will need to work on (roughly). Indication for each one which use case will be a must/should/nice to have would help you to make a better plan. Indicating also which performance test could be done at each step would also be useful. Note that a plan is there to help you not constraint you. Let me know if you want I help you on this. Best, Vicente

Thanks for the comments! Vicente:

Concerning the project proposal, I would like to see the following points more elaborated:

I've updated the goals accordingly. I couldn't figure out what do you mean by configuring thread pools. I would like to use boost::threads executors. (The user might use something else with the same interface)

Concerning the millstones, I would prefer a week based schedule and that as far as possible each iteration includes something adding value with the code the tests and the documentation.

I broke it down to weeks, it's much clearer now. Niall:

Do run it through a spell checker as there are quite a few typos. I forgot about this, thanks for pointing it out.

I'll be watching with close interest as you're basically implementing a batch-capable superset of what I proposed as a monadic continuations framework for AFIO. If you do well, I may even just adapt your work into AFIO actually, it would save me a ton of work, so I'm definitely hoping you get funding! Let's have a quick chat about it upon funding!

Thanks, Benedek