dangling pointer

More documents

Recommendations

Info

std::auto_ptr and Generic Codetemplatevoid foo(T arg){T temp(arg);// use temp// use arg}std::auto_ptr is obviously not suitable as a template argument for foo().But it is not possible to express that in a natural way.
std::auto_ptr and Generic Code (cont.)std::unique_ptr uses rvalue references to express its behavior properly. Inthe code above, the lineT temp(arg);does not compile with T == std::unique_ptr.You’d have to sayT temp(std::move(arg));The use of std::move expresses that it is not ok to use arg again. Now usingarg on a subsequent line would be an obvious mistake even in the generic code.In summary, in C++0x you can write generic code in such a way that what doesn’twork for std::unique_ptr won’t compile for std::unique_ptr.You can do even better with concepts: generic code that works forstd::unique_ptr requires movability, as opposed to copyability.
Page 1 and 2: The Boost Smart PointerLibraryThoma
Page 3 and 4: Contents of the Boost Smart Pointer
Page 5 and 6: The ProblemTraditional “managemen
Page 7 and 8: Null PointersC/C++ raw pointers hav
Page 9 and 10: Reassigning a shared_ptrboost::shar
Page 11 and 12: Pragmatism First (cont.)boost::shar
Page 13: Handling HandlesCustom deleters can
Page 18 and 19: Leaking Memory with Smart PointersT
Page 20 and 21: struct B;struct A {boost::shared_pt
Page 22 and 23: oost::shared_arrayIn C/C++, there a
Page 25 and 26: oost::scoped_arrayboost::scoped_arr
Page 27: Cyclic References and SymmetryIn pr
Page 30 and 31: oost::weak_ptr Creation and Resetti
Page 32 and 33: oost::weak_ptr Object Access (cont.
Page 34 and 35: Weak Pointers Relations Can Be Tric
Page 36 and 37: oost::intrusive_ptrboost::intrusive
Page 38 and 39: std::auto_ptr (cont.)Use std::auto_
Page 42 and 43: Setting up Weak Pointer Relationscl
Page 44 and 45: How to enable shared from thisIf we

dangling pointer

Create successful ePaper yourself

Delete template?

Save as template?