Sergey Gromov wrote: > The only thing copy-construction is useful for is implementing move > semantics, think std::auto_ptr. Seems like everything else can be done > in post-blit.
The "linked list" implementation of smart pointers also requires a copy constructor. It's (arguably) not a very good design, but it is a valid design. > The inability to overload opAssign(typeof(this)) is a blocker for robust > RAII though. Yes. -- Rainer Deyke - [email protected]
