🚀 go-pugleaf

|> Go ahead, shoot me down!

POW!

Seriously, how can the compiler tell when deep-copy is or isn't needed.  You
can help it, however, by using auto_ptr for the 'external' parts of an object
(i.e., those logically part of it but included through a pointer; this term is
my own so don't expect others to use it; I am looking for a better term). 

With auto_ptr's in place your relocate operation is a breeze -- just copy the
object with a copy constructor and placement new.

This seems to be an ideal application for certain semantics of auto_ptr that
have been considered to be offensive.  To be maximally const-correct your
class will need a non-const copy constructor.

-- 
John Hickin      Nortel Technology, Montreal, Quebec
(514) 765-7924   hickin@bnr.ca
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  Moderation policy:
  http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]