[gclist] Fast-allocating non-copying GC's

[Geert Bosch]

On Tue, 19 Mar 1996 10:35:10 -0500 Bob Duff wrote:
`` You seem to be talking about multiple storage pools 
   of a given kind. This seems strange to me.  Why not 
   have a single pool for each size of object?  If it 
   runs out, it will snarf another page from the "main
   pool". ''

In many cases there won't be a necessary relationship
between different pools of the same type. Forcing these
pools to be one pool which consists of several pieces
together limits flexibility.

And Ada also allows the user to instantiate pools. An
abstract data type might want to use a private storage 
pool to be able to prevent out-of-memory conditions
during a critical database update for example. 

An application might also want to use a Mark-Release pool.
It certainly would not be a good idea to use one 
Mark-Release pool when the user specified that there should
be two seperate pools.