dcpp::shared_device is a class of duckcpp. The dcpp::shared_device object holds underlying dcpp::DuckcppDevice pointer and a reference-counter. When another object of dcpp::shared_device is bound to the existed object of dcpp::shared_device, they share the same underlying dcpp::DuckcppDevice pointer and the same reference counter, and their reference-counter is increased by one. It will handle exception.

Important Notice

What dcpp::shared_device does:

What reference counter counts:

For example:

4 objects are hooked together to use same underlying device,
but the device is removed,
so all of the 4 objects' reference counter is zero.

Differs from dcpp::IReferenceCounted

dcpp::shared_device has different purpose with dcpp::IReferenceCounted.

dcpp::IReferenceCounted is used as base class by many classes of duckcpp core layer, which is written and forked from irrlicht. All objects of those classes must be created and referenced as pointer. Without careful management, those pointers are very easy to crash program. The referenced objects can be dereferenced by calling "object->drop()". They are still very important parts of the engine, and will keep in the codebase.

dcpp::shared_device is a class not designed for using as pointer. The words "shared" and "reference counter" mean it shares the underlying held "dcpp::DuckcppDevice *" pointer and counts how many objects shared the same "dcpp::DuckcppDevice *" pointer, not the dcpp::shared_device object itself. When one of the shared objects of dcpp::shared_device is hitting to its end point of lifetime, the reference counter will be counted down by one. If the underlying device (aka, the "dcpp::DuckcppDevice *" pointer) is destroyed at some point, it will be detected and the reference counter of all shared objects of dcpp::shared_device is reset to zero, although those objects are still valid.

Not Pointer

dcpp::shared_device is not designed for using as pointer, it can be constructed directly.

Back

Up

c++

Duckcpp

cppfx.xyz