Re: [boost] Composing non copyable and movable classes

7 Dec 2008

      On Sat, Dec 6, 2008 at 4:42 PM, David Abrahams <dave@boostpro.com> wrote:
...
This feels like overgeneralizing.  Unless otherwise justified, every
type should have value semantics, i.e., should be movable and copiable.
I find C-style incomplete type (and therefore non-copyable,
non-movable and non-value) handles quite practical too:

//foo.h
namespace boost { template <class> class shared_ptr; }
struct handle;
boost::shared_ptr<handle> create_handle();
void do_something( handle & );

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode