Memory Management Scheme for TSIMMIS

This is a result of of a discussion between Joachim, Ramana and Yannis on 09/25/1996, refined by Michael, Murty and Ramana on 08/15/97.

In order to avoid and fix memory leaks we decided to follow this approach:

  1. New software should always deallocate memory which it dynamically allocates. Best is, if new components are implemented as C++ classes where memory which cannot be reclaimed within a procedure (method) can be freed by the class destructor.
  2. Old software should eventually be using alloc and free calls of a special memory management class which allocates and manages a large memory block which can easily be reclaimed to avoid memory leaks.


Last updated: 1997-Aug-20
Michael Rys < rys@db.stanford.edu >