| FBB::fswap(3bobcat) | Fast swap function | FBB::fswap(3bobcat) |
FBB::fswap - generic template fast swap function
#include <bobcat/fswap>
The information stored in objects frequently needs to be swapped. A well-known example is the swapping operation required when implementing an overloaded assignment operator. For example, the generic form of the operator assignment operator is:
Class &operator=(Class const &other)
{
Class tmp(other);
swap(tmp);
return *this;
}
The swap functionality merely swaps the content of the current object and another object. The standard std::swap function calls the class’s operator= function to swap objects. Newer implementations might use move-operations to increase the speed of the swapping operation, but in both cases some form of the assignment operator must be available. Swapping, however, might be possible when assignment isn’t. Classes having reference data members usually don’t offer assignment operators but swapping might be a well-defined operation.
It is well known that objects can be installed in a block of memory using placement new, using a block of memory the size of the object to construct the object it. This is the foundation of the template function FBB::fswap (fast swap). This swap function merely uses the memory occupied by objects to implement the swapping operation and it may therefore be used with classes having const data members, reference data members, ponters to allocated memory etc, etc. The function simply uses a spare block of memory the size of the object to be swapped. It then uses memcpy(3) to swap the information contained in the two objects, using the spare block of memory as a placeholder.
Classes may define data members that do not support fast swapping. If such data members can be swapped using either std::swap or their own swap member, then overloaded versions of fswap can be used to fast-swap objects of such classes. Also, classes may inherit from base classes that do not support fast-swapping, but that either offer their own swap members or can be swapped using std::swap. For these cases overloaded versions of fswap are also available. The classes std::string and std::unordered_map are examples of classes whose objects might not be swappable using a fast swap method. Therefore, in practice, classes defining members of such classes should use one of the overloaded fswap functions for swapping their objects.
FBB
All constructors, members, operators and manipulators, mentioned in this
man-page, are defined in the namespace FBB.
-
The enumereation SwapMode is used to specify a specific swapping-method:
#include <iostream> #include "../fswap" using namespace FBB;
// Demo class, members d_v3 and d_v4 cannot be memcpy-fast swapped
// class Demo {
size_t d_v1;
size_t d_v2;
std::string d_v3;
std::string d_v4;
size_t d_v5;
public:
Demo(size_t value = 0);
void show(char const *msg);
void swap(Demo &rhs); }; Demo::Demo(size_t value) :
d_v1(value),
d_v2(value + 1),
d_v3(std::to_string(value + 2)),
d_v4(std::to_string(value + 3)),
d_v5(value + 4) {}
// fast-swap 2 objects, except for d_v3 and d_v4, which are
// swapped by either std::swap or their own .swap() members
// void Demo::swap(Demo &rhs) {
// This is OK, after commenting out the // fswap(*this, rhs); // string members
// specifying members that should be swapped
// using std::swap. These members MUST be
// specified in their class declaration order
fswap(*this, rhs, d_v3, d_v4); // fswap(*this, rhs, d_v4, d_v3); // this won’t work...
// same, explicitly requesting the
// swap-mode // fswap<SwapMode::SWAPMEMBER>(*this, rhs, d_v3, d_v4);
// explicitly requesting another
// swap-mode // fswap<SwapMode::STDSWAP>(*this, rhs, d_v3, d_v4);
// default, starting at a begin-member
// NOTE: the example does NOT swap d_v1 // fswap(&d_v2, *this, rhs, d_v3, d_v4);
// use fastswap, but start at the
// member d_v1 (use this for derived
// classes whose base class do not
// support fast swapping.
// Before using this example comment
// out the class’s std::string members // fswap(&d_v1, *this, rhs, d_v3);
// same, explicitly requesting the
// swap method, swapping all // fswap<SwapMode::SWAPMEMBER>(&d_v1, *this, rhs, d_v3, d_v4);
// explicitly requesting another
// swap-mode // fswap<SwapMode::STDSWAP>(&d_v1, *this, rhs, d_v3, d_v4);
// use stdswap by default, but not
// for d_v4, for which .swap() is
// used // fswap(&d_v1, *this, rhs, d_v3, swapmember(d_v4));
// same // fswap<SwapMode::STDSWAP>(&d_v1, *this, rhs, d_v3, // swapmember(d_v4));
// explicitly requesting the already
// default swap method is OK // fswap(&d_v1, *this, rhs, swapmember(d_v3), stdswap(d_v4)); } void Demo::show(char const *msg) {
std::cout << msg << ". " << d_v1 <<
", " << d_v2 <<
", " << d_v3 <<
", " << d_v4 <<
", " << d_v5 <<
’\n’; } using namespace std; int main() {
Demo d1(10);
Demo d2(20);
d1.show("This is d1:");
d2.show("This is d2:");
cout << "swapping...\n";
d1.swap(d2);
d1.show("This is d1:");
d2.show("This is d2:"); }
bobcat/fswap - defines the class interface
The fswap functions should not be applied mechanically to swap objects of classes having pointer data members defining, e.g., a linked list. Consider a list of four objects like:
A -> B -> C -> D
fast-swapping B and C would result in the following corrupted list:
+------+
| |
A -> C -+ +-> B -+ +-> D
| |
+-------------+
However, classes implementing a data structure like a linked-list might still benefit from fast swapping operations: by implementing their own swap member they could first use fast swapping to swap the objects, followed by another fast swap to unswap their `next’ pointers.
The fswap function should also not be used for objects defining (back-)pointers to their own data. Consider the following objects using pointers to data and (back-)pointers to the original objects:
After the swap **Bimp should point to Bimp’s address (now at A), but in fact it points to Aimp’s address (now at B). Likewise, the back pointers still point at their original objects rather than at their swapped objects.
Before fswapping:
A B
+--------+ +-----------+ +--------+ +-----------+
| | | | | | | |
+--> *Aimp------> *A (back)--+ +--> *Bimp------> *B (back)--+
| | | | | | | | | | | |
+--**Aimp | +-----------+ | +--**Bimp | +-----------+ |
+--------+ <---------------+ +--------+ <---------------+
After fswapping:
+-------------------------------+
+--|-------------------------------|-+
+-------------|--|-----------------+ | |
| A | v | B | v
| +--------+ | +-----------+ | +--------+ | +-----------+
| | | | | | | | | | | |
+-----> *Bimp---+ | *A (back)--+ +---> *Aimp---+ | *B (back)--+
| | | | | | | | | | | |
| +---**Bimp | +-----------+ | +---**Aimp | +-----------+ |
| +--------+ <---------------+ | +--------+ <---------------+
+------------------------------------+
All stream classes define such pointers and can therefore not be swapped using fswap.
The bottom line being that fswap should only be used for self-defined classes for which it can be proven that fast-swapping does not corrupt the values of its pointer data.
Bobcat is an acronym of `Brokken’s Own Base Classes And Templates’.
This is free software, distributed under the terms of the GNU General Public License (GPL).
Frank B. Brokken (f.b.brokken@rug.nl).
| 2005-2020 | libbobcat-dev_5.07.00 |