Re: Allocators and exceptions

[Georg Bauhaus <rm.tsoh+bauhaus@maps.futureapps.de>]

On Tue, 2007-09-11 at 12:07 -0700, Maciej Sobczak wrote:

> But... did I mention that C++ handles this issue correctly? ;-)
> And no, it does not have any super-capable access types. A little bit
> smarter allocator is enough.

C++ doesn't seem to handle deallocation etc. of sibling components
either, so I'm not sure I understand. Isn't this a rather special
case you are describing?
 Should the following be excluded from consideration? (The program
quickly claims all available memory, as I would have expected; any
pointers to what should I read to learn how this can be simply
prevented in C++?)


class T {
   int c;
   int *x;
public:
   T(int init) {
      x = new int[1024];
      if (init < 1) { throw "Constraint_Error"; }
      c = init;
   }
   ~T() {
      delete[] x;
   }
};

typedef T* T_access;

int main()
{
   T_access ptr;

   while (1) {
      try {
         ptr = new T(-5); 
         delete ptr;
      } catch (...) {
         // all is well?
      }
   }
   return 0;
}