On Wed, Nov 14, 2012 at 11:00 AM, Rob Stewart <robertstewart@comcast.net>wrote:
Why must child be copyable? Just because the underlying implementation permits it doesn't mean that you must permit it in your abstraction.
I don't understand why it should be either. To me it should be movable only, and as someone suggested, the id could be copyable as it's only a value. As other suggested, to me I will not agree with boost process interface if it don't provide consistent behaviour between platforms, even if it have different costs between platforms. The point is to write the code in one way and then possibly have specific code if you want to do platform specific code. In my case I don't case how it works inside as long as I don't have to have separate code for different platforms. I thought it was the primary goal of the library? The suggestions going to default behaviour but optional constructor arguments to help with platform specific behaviours seems going to the right direction. Joel Lamotte