mbed library sources. Supersedes mbed-src.
Fork of mbed-dev by
NonCopyable< T > Class Template Reference
Inheriting from this class autogeneration of copy construction and copy assignment operations. More...
#include <NonCopyable.h>
Protected Member Functions | |
NonCopyable () | |
Disallow construction of NonCopyable objects from outside of its hierarchy. | |
~NonCopyable () | |
Disallow destruction of NonCopyable objects from outside of its hierarchy. | |
MBED_DEPRECATED ("Invalid copy construction of a NonCopyable resource.") NonCopyable(const NonCopyable &) | |
NonCopyable copy constructor. | |
MBED_DEPRECATED ("Invalid copy assignment of a NonCopyable resource.") NonCopyable &operator | |
NonCopyable copy assignment operator. | |
NonCopyable & | operator= (const NonCopyable &) |
Declare copy assignment operator as private, any attempt to copy assign a NonCopyable will fail at compile time. |
Detailed Description
template<typename T>
class mbed::NonCopyable< T >
Inheriting from this class autogeneration of copy construction and copy assignment operations.
Classes which are not value type should inherit privately from this class to avoid generation of invalid copy constructor or copy assignment operator which can lead to unnoticeable programming errors.
As an example consider the following signature:
class Resource; class Foo { public: Foo() : _resource(new Resource()) { } ~Foo() { delete _resource; } private: Resource* _resource; } Foo get_foo(); Foo foo = get_foo();
There is a bug in this function, it returns a temporary value which will be byte copied into foo then destroyed. Unfortunately, internally the Foo class manage a pointer to a Resource object. This pointer will be released when the temporary is destroyed and foo will manage a pointer to an already released Resource.
Two issues has to be fixed in the example above:
- Function signature has to be changed to reflect the fact that Foo instances cannot be copied. In that case accessor should return a reference to give access to objects already existing and managed. Generator on the other hand should return a pointer to the created object.
// return a reference to an already managed Foo instance Foo& get_foo(); Foo& foo = get_foo(); // create a new Foo instance Foo* make_foo(); Foo* m = make_foo();
- Copy constructor and copy assignment operator has to be made private in the Foo class. It prevents unwanted copy of Foo objects. This can be done by declaring copy constructor and copy assignment in the private section of the Foo class.
class Foo { public: Foo() : _resource(new Resource()) { } ~Foo() { delete _resource; } private: // disallow copy operations Foo(const Foo&); Foo& operator=(const Foo&); // data members Resource* _resource; }
Another solution is to inherit privately from the NonCopyable class. It reduces the boiler plate needed to avoid copy operations but more importantly it clarifies the programmer intent and the object semantic.
class Foo : private NonCopyable<Foo> { public: Foo() : _resource(new Resource()) { } ~Foo() { delete _resource; } private: Resource* _resource; }
- Template Parameters:
-
T The type that should be made non copyable. It prevent cases where the empty base optimization cannot be applied and therefore ensure that the cost of this semantic sugar is null.
As an example, the empty base optimization is prohibited if one of the empty base class is also a base type of the first non static data member:
struct A { }; struct B : A { int foo; }; // thanks to empty base optimization, sizeof(B) == sizeof(int) struct C : A { B b; }; // empty base optimization cannot be applied here because A from C and A from // B shall have a different address. In that case, with the alignment // sizeof(C) == 2* sizeof(int)
The solution to that problem is to templatize the empty class to makes it unique to the type it is applied to:
template<typename T> struct A<T> { }; struct B : A<B> { int foo; }; struct C : A<C> { B b; }; // empty base optimization can be applied B and C does not refer to the same // kind of A. sizeof(C) == sizeof(B) == sizeof(int).
- Note:
- Compile time errors are disabled if the develop or the release profile is used. To override this behavior and force compile time errors in all profile set the configuration parameter "platform.force-non-copyable-error" to true.
Definition at line 150 of file NonCopyable.h.
Constructor & Destructor Documentation
NonCopyable | ( | ) | [protected] |
Disallow construction of NonCopyable objects from outside of its hierarchy.
Definition at line 155 of file NonCopyable.h.
~NonCopyable | ( | ) | [protected] |
Disallow destruction of NonCopyable objects from outside of its hierarchy.
Definition at line 159 of file NonCopyable.h.
Member Function Documentation
MBED_DEPRECATED | ( | "Invalid copy construction of a NonCopyable< T > resource." | ) | const [protected] |
NonCopyable copy constructor.
A compile time warning is issued when this function is used and a runtime warning is printed when the copy construction of the non copyable happens.
If you see this warning, your code is probably doing something unspecified. Copy of non copyable resources can lead to resource leak and random error.
Definition at line 171 of file NonCopyable.h.
MBED_DEPRECATED | ( | "Invalid copy assignment of a NonCopyable< T > resource." | ) | [protected] |
NonCopyable copy assignment operator.
A compile time warning is issued when this function is used and a runtime warning is printed when the copy construction of the non copyable happens.
If you see this warning, your code is probably doing something unspecified. Copy of non copyable resources can lead to resource leak and random error.
NonCopyable& operator= | ( | const NonCopyable< T > & | ) | [protected] |
Declare copy assignment operator as private, any attempt to copy assign a NonCopyable will fail at compile time.
Generated on Tue Jul 12 2022 20:37:48 by 1.7.2