Re: [Boost-users] [iostreams and serialization] serialize via iostreams

On 16/01/2008, Jonathan Turkanis wrote:

...

The problem is that when I do this, the code ends up calling a copy constructor (which doesn't exist) on my SocketDevice class. However I don't want to implement a copy constructor for this class as it doesn't make sense (as it manages a socket and a buffer for that socket, etc).

Currently, except for standard streams and stream buffers, which are given special treatment, Boost.Iostreams fitlers and devices must be copy constructible. (See, e.g., the documentation for the template parameter T here: http://www.boost.org/libs/iostreams/doc/index.html?path=3.3)

Thanks for the information, that clarifies things for me.