Thread: Interlocked refcounting and possible crash

I would avoid Borland C++. It is obviously not very good compared to other free compilers (such as GCC and Visual C++ which both have C++0x support).

You are right, but I am very used to it, and I am slowly getting used to the others. C++0x Support in GCC - GNU Project - Free Software Foundation (FSF)
and it hasn't full C++0x support.

Why not just put the critical section and ref count inside the pointer class itself

Ref count inside object does not require additional heap operations.
Always 1 critical section per critical data, especially when I want to make a lot of pointers.
Additionally, making this class virtual avoids deleting pointers of incomplete types (resulting in undefined behaviour) that I have already encountered.

why you would want to use a class for this special purposes at all?

I want to have a pure and widely used garbage collector. Boost's implementation has a couple of things that annoy me or I just dont need.

Because it seemed the class did little--if anything--good

That's exactly what I need and will help me a lot

Originally Posted by kmdv

You are right, but I am very used to it, and I am slowly getting used to the others. C++0x Support in GCC - GNU Project - Free Software Foundation (FSF)
and it hasn't full C++0x support.

But like you see, it's slowly getting there
So why not start using them?

As for the rest... I didn't question your need for a smart pointer. I questioned the need for wrapping your critical section in a make_threaded class.
Those might have been better put in the Block of your smart pointer class and handled from there, because it seems that your make_threaded class provides no additional benefits.