On Wed, 4 May 2011, Kirk, Benjamin (JSC-EG311) wrote: > Looking back at our AutoPtr<>, is is a ripoff of the gcc 3.2.1 > implementation to get around some compiler-specific weirdness from many > years ago. Seems like by now we should be able to rely on std::auto_ptr<>. > > What do you think about replacing AutoPtr<> with std::auto_ptr<> throughout > the code? Simply typedef'ing std::auto_ptr<> to libMesh::AutoPtr<> should > be sufficient to allow old user code to still compile...
Seems like a change with next-to-zero net loss: if your compiler isn't C++98 compliant now, it's time to put a bullet in it. But it also seems like a change with zero net win. What's the gain? Besides, std::auto_ptr is supposed to be deprecated once C++0x-er-1x comes out (any decade now!); we might as well keep our AutoPtr as a shim to whatever "std::unique_ptr" subcategory they have replacing it. --- Roy ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
