Re: [Boost-users] noncopyable

AMDG Hicham Mouline wrote:

AFAIU, deriving from boost::noncopyable disables _accidental_ object copying.

Is it possible to implement a clone() const member function of the object to _explicitly_ get a copy of the object?

Perhaps deriving boost::noncopyable makes it totally impossible to ever get a copy of an object without resorting to byte copy.

boost::noncopyable has a private copy constructor and copy assignment operator. This prevents the compiler from generating a copy constructor and assignment operator for derived classes. That's all noncopyable does. If you want a clone function, the easiest way is probably to implement a private copy constructor and have clone call it. In Christ, Steven Watanabe