From 3639793133103297082 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,695bc9edfbdd4b9a X-Google-Attributes: gidf78e5,public From: aGriffiths@ma.ccngroup.com (Alan Griffiths) Subject: Re: auto_ptr and explicit Date: 1997/04/01 Message-ID: <82256860wnr@ma.ccngroup.com>#1/1 X-Deja-AN: 229986349 References: <01bc3e0f$8e5de140$636749ce@valhala> X-Mail2News-User: aGriffiths@ma.ccngroup.com X-Original-Date: Tue, 01 Apr 1997 10:50:09 GMT X-Mail2News-Path: devmaccn.demon.co.uk X-Broken-Date: Tuesday, Apr 01, 1997 11.04.15 GMT Organization: CCN Market Analysis X-Auth: PGPMoose V1.1 PGP comp.std.c++ Reply-To: aGriffiths@ma.ccngroup.com Newsgroups: comp.std.c++ Originator: austern@isolde.mti.sgi.com In article: <01bc3e0f$8e5de140$636749ce@valhala> "Guy Gascoigne - Piggford" writes: > On a related note. How do you publicise the use of auto_ptr from outside > the std namespace. Simply typing > > using std:auto_ptr; > > doesn't work, my compiler requires that I do this; Your compiler is broken! > using std:auto_ptr; > > and repeat this for every templated instantiation I use. So is there a > syntax that avoids this problem? Your compiler is broken! (My sympathy, the (MSVC) compiler I have to use is broken the same way.) Possible solutions: o You could implement an auto_ptr clone in global namespace. o I've not tried "typedef std::auto_ptr auto_ptr" as I mistrust the "standard" smart pointer design changes - but it _should_ work. (I believe the design of "std::auto_ptr" is currently an "outstanding issue" against the UK delegation). __ Alan Griffiths | Work : agriffiths@ma.ccngroup.com Senior Systems Consultant, | Tel. : +44 115 934 4517 CCN Group Limited. | Home : alan@octopull.demon.co.uk (ACCU C++ SIG organiser) | (ACCU: http://bach.cis.temple.edu/accu) --- [ comp.std.c++ is moderated. To submit articles: Try just posting with your newsreader. If that fails, use mailto:std-c++@ncar.ucar.edu comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html Comments? mailto:std-c++-request@ncar.ucar.edu ]