🚀 go-pugleaf

Bill Gibbons (bgibbons@taligent.com) wrote:

|> Taligent has had years of experience using a variety of templates which
|> are variants of auto_ptr.  The consensus here is that auto_ptr must have
|> ownership semantics, and they must be enforced by the assignment operator
|> and copy constructor.

While I've certainly less experience than Taligent, this was my feeling,
too.

So how do you do it: as I do, by casting away const in the assignment
operator and the copy constructor, or do you have some other trick?  (I
would love to find a better solution, since I think that Fergus'
concerns about this solution *are* valid.)
-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils en informatique industrielle--
                             --Beratung in industrieller Datenverarbeitung
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]