vo001_AdoptOrOwnMemory.C File Reference

Detailed Description

In this tutorial we learn how the RVec class can be used to adopt existing memory or allocate some.

 
// We use this class for didactic purposes: upon copy, a line is printed to the terminal.
class UponCopyPrinter {
public:
   UponCopyPrinter() = default;
   UponCopyPrinter(UponCopyPrinter &&) = default;
   UponCopyPrinter(const UponCopyPrinter &) { std::cout << "Invoking copy c'tor!" << std::endl; }
};
 
void vo001_AdoptOrOwnMemory()
{
 
   // One of the essential features of RVec is its ability of adopting and owning memory.
 
   // Let's create an RVec of UponCopyPrinter instances. We expect no printout:
   ROOT::RVec<UponCopyPrinter> v(3);
 
   // Let's adopt the memory from v into v2. We expect no printout:
   ROOT::RVec<UponCopyPrinter> v2(v.data(), v.size());
 
   // OK, let's check the addresses of the memory associated to the two RVecs It is the same!
   std::cout << v.data() << " and " << v2.data() << std::endl;
 
   // Now, upon reallocation, the RVec stops adopting the memory and starts owning it. And yes,
   // a copy is triggered. Indeed internally the storage of the RVec is an std::vector. Moreover,
   // the interface of the RVec is very, very similar to the one of std::vector: you have already
   // noticed it when the `data()` method was invoked, right?
 
   v2.push_back(UponCopyPrinter());
 
   // Of course, now the addresses are different.
   std::cout << v.data() << " and " << v2.data() << std::endl;
}

 
0x7fffab802aa0 and 0x7fffab802aa0
0x7fffab802aa0 and 0x4ed2970

Date

May 2018

Author

Danilo Piparo

Definition in file vo001_AdoptOrOwnMemory.C.