Re: Smart Pointers and Microsoft Foundation Classes
Well I could post my reference counter code, it's a standard approach to a
simple counted pointer template I wrote last night to better illustrate my
thinking. This code works fine in a single threaded application as is. I was
pondering the move to using this kind of abstraction in a multithreaded
situation.
#ifndef counted_pointer_h
#define counted_pointer_h
// class for counted reference semantics
// deletes the object to which it refers when the last CountedPtr that
refers to it is destroyed
template <class T>
class CountedPtr {
public:
// initialize pointer with existing pointer
// requires that the pointer p is a return value of new
explicit CountedPtr (T* p=0): ptr(p), count(new long(1)) {}
// copy pointer (add another owner)
CountedPtr (const CountedPtr<T>& p) throw(): ptr(p.ptr),
count(p.count) {
++*count;
}
// destructor (if this was the last owner)
~CountedPtr () throw() {
dispose();
}
// assignment (unshare old and share new value)
CountedPtr<T>& operator= (const CountedPtr<T>& p) throw() {
if (this != &p) {
dispose();
ptr = p.ptr;
count = p.count;
++*count;
}
return *this;
}
// access the value to which the pointer refers
T& operator*() const throw() {
return *ptr;
}
T* operator->() const throw() {
return ptr;
}
private:
T* ptr; // pointer to the value
long* count; // shared number of owners
void dispose() {
if (--*count == 0) {
delete count;
delete ptr;
}
}
};
#endif // counted_pointer_h
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:r59mr3pu9c2sqhuaadps3o1r9ie67nklp8@4ax.com...
I had to create my own reference-counted pointer class because none of the
classes I could
find (a couple years ago) handled reference-counted semantics.
Because I knew there were several kinds of "smart pointers" around, which
all had
different semantics, I decided that anyone who used this term without
actualy saying
std::auto_ptr or boost::shared_ptr probably didn't understand even the
basic problems
involved.
joe
On Tue, 19 Feb 2008 11:26:17 -0600, "Doug Harrison [MVP]" <dsh@mvps.org>
wrote:
On Tue, 19 Feb 2008 11:42:47 -0500, Joseph M. Newcomer
<newcomer@flounder.com> wrote:
"Joseph M. Newcomer" <newcomer@flounder.com> ha scritto nel messaggio
news:o65lr31ims8isd5klmg68vfov39cberave@4ax.com...
Smart pointers do not maintain reference counts, as
far as I can tell
If the boost library is being used, SURELY the OP would have said "In
using
boost::shared_ptr..."
joe
I think Giovanni's point was that "smart pointer" is a pretty generic
term.
For example, I named the smart pointer classes I wrote 10 years ago due to
dissatisfaction with std::auto_ptr "nc_ptr" and "rc_ptr", where "nc" means
"Non-Copyable" and "rc" means "Reference-Counted". It's really
std::auto_ptr that is the oddball here; its weird (though very
occasionally
useful) copy semantics are sort of an unsatisfactory compromise between NC
and RC, which happens sometimes when a standards group invents something.
Concerning the OP's post, I kind of gave up when he said he was using
smart
pointers "to guard against the issues of multithreaded processes". That
didn't make any sense to me. Also, when he said, "I do not know if my
pointer is unique and owns the object or whether it's a shared pointer to
the pointee object or whether it's a copy on write type of object", the
answer to that is, if he needs to know those things, he should use a smart
pointer class that supports them. The Boost library offers several types
of
smart pointers with different capabilities that may help that aspect of
his
problem.
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm