用于C ++ 11中RAW指针的SMART向量？

Question

I'm using an old open-source library, with the following (simplified) API of interest:

// some class that holds a raw pointer to memory on the heap
// DOES NOT delete it in its destructor
// DOES NOT do a "deep" copy when copied/assigned (i.e., after copying both objects
// will point to the same address)
class Point;

// function used to construct a point and allocate its data on the heap
Point AllocPoint();
// function used to release the memory of the point's data
void DeallocPoint(Point& p);

// Receives a pointer/c-array of Points, along with the number of points
// Doesn't own the memory
void Foo(Point* points, int npts);

What's the best (safest/most readable/most elegant) way of using this API in C++11. I can't simply use vector<unique_ptr<Point, PointDeleter>> (where PointDeleter is a simple custom deleter I can implement), because then I will not be able to use the function Foo (which expects Point* and not unique_ptr<Point>* ).

Thanks

Answer 1

If you really want to make it look nice, you're probably going to have to write a set of really comprehensive wrappers which completely hide the library's API - effectively, wrap the entire library with one that behaves in a modern C++ way on the outside and hides all the mess inside.

Not a pleasant task, but if you can get the behaviour of that library right then it should make your life a lot easier in the long term. Might not be worth it if you're not going to use this external library very extensively though.

Answer 2

I would wrap this non-RAII C-like API in RAII building blocks, and then use them in C++11 code.

For example: you can define a RaiiPoint class that wraps the (non-RAII) Point class, and in its constructor calls AllocPoint() , in the destructor DeallocPoint() . Then you can define proper copy constructor and copy operator= , or just implement move semantics (with move constructor and move operator= ), or make the wrapper class both copyable and movable, basing on your requirements.

Then you can simply use a std::vector<RaiiPoint> with your RAII-based wrapper class.

(This is a general approach that you can use when you want to use C libraries in modern C++ code: you can wrap the "raw" C library handles and objects in safe RAII boundaries, and use these robust safe wrapper classes in your modern C++ code.)

Answer 3

You can use std::vector<Point> , calling Foo( &v[0], v.size() ) . But managing the memory here could be tricky, since Point apparently doesn't provide any clean copy and assignment; a custom deleter in the allocator will be called for each element, even if it is copied.

If the vector should actually own the points, then you can wrap it in a more complex class, which calls AllocPoint for each insertion (and inserts the results), and DeallocPoint for each removal (and for everything remaining in the vector on destruction). This class should not allow write access to the Point (non-const operator[] , non-const iterators, etc.), however, since this would allow changing any pointers in Point , and loosing what is needed for DeallocPoint to work correctly. Presumably, there other functions for manipulating Point ; you'll have to arrange for these to be available through the wrapper interface.

Answer 4

"You" could write a simple wrapper to free the memory:

struct PointVectorWrapper {
  vector<Point> points;
  ~PointVectorWrapper() {
    for (Point& p : points) {
      DeallocPoint(p);
    }
  }
  PointVectorWrapper& operator=(const PointVectorWrapper&) = delete;
  PointVectorWrapper(const PointVectorWrapper&) = delete;
};
// Now the usage is simple and safe:
PointVectorWrapper points;
// ... populate points ...
Foo(points.data(), points.size())

But this seems a little "adhoc". What's a more standard/reusable solution?

Answer 5

You could use a standard vector with a custom allocator, that invoke AllocPoint on construct method and DeallocPoint() on destruct method.

template<typename T>
class CustomAllocator : public std::allocator<T>
{
  //Rebind and constructors
};

template<>
class CustomAllocator<Point> : public std::allocator<Point>
{
   //Rebind and constructors

   //For c++11
   void construct( pointer p )
   {
      new (p) Point();
      *p = AllocPoint();
   }

   void construct( pointer p, const_reference val )
   {
      construct(p);
      //copy member from val to point if neccessary 
   };   


   void destroy( pointer p )
   {
      DeallocPoint(*p);
      p->~Point();
   }
};

typedef std::vector<Point, CustomAllocator<Point> > PointVector;