A page on smart pointer timings will be of interest to those curious about performance issues.
+A page on smart pointer programming techniques lists
+ some advanced applications of shared_ptr and weak_ptr.
Common Requirements
These smart pointer class templates have a template parameter, T, which specifies the type of the object pointed to by the smart pointer. The behavior diff --git a/sp_techniques.html b/sp_techniques.html index e523a52..a157f0b 100644 --- a/sp_techniques.html +++ b/sp_techniques.html @@ -1,12 +1,12 @@
-
Smart
- pointer programming techniques
+ Pointer Programming Techniques
Using incomplete classes for implementation hiding
The "Pimpl" idiom
Using abstract classes for implementation hiding
@@ -615,7 +615,10 @@ public:
Note that shared_lock is not templated on the mutex type, thanks to
shared_ptr<void>'s ability to hide type information.
Using shared_ptr to wrap member function calls
- [http://www.research.att.com/~bs/wrapper.pdf]
+shared_ptr implements the ownership semantics required from the Wrap/CallProxy
+ scheme described in Bjarne Stroustrup's article "Wrapping C++ Member Function
+ Calls" (available online at http://www.research.att.com/~bs/wrapper.pdf).
+ An implementation is given below:
template<class T> class pointer
{
private:
@@ -631,7 +634,7 @@ public:
shared_ptr<T> operator->() const
{
p_->prefix();
- return shared_ptr<T>(p_, mem_fn(&T::suffix));
+ return shared_ptr<T>(p_, mem_fn(&T::suffix));
}
};