Re: Ada 0Y plans for garbage collection?

["Robert I. Eachus" <rieachus@attbi.com>]

Martin Krischik wrote:

 > But for it to work realy user friendly, would you not need compiler
 > support? Everytime a new access is created or destroyed the compiler
 > would need to tell the storrage pool.
 >
 > Remember: controlled types where considered not user friendly. If I
 > undersand the OP right he wants:
 >
 > type Some_Access is access Some_Type; for Some_Access'Storrage_Pool
 > use Ada.Reference_Counted__Pools.Pool;
 >
 > the rest need to be done by the compiler.

All that is currently allowed.  Well technically, it should be

My_Storage_Pool: Reference_Counted_Storage_Pool;

type Some_Access is access Some_Type;
for Some_Access'Storage_Pool use My_Storage_Pool;

...but that is a detail.  Should we require such a storage pool type in
Ada 200Y? I think it would be a good idea.  But requiring that there be
an instance of such a pool might not be a good idea.

And I tend to like my current implementation, where I create a pool by 
instantiating a generic package, with the size of each allocated object, 
and the number of objects in the heap.  It has a very low overhead for 
allocate and free.  (And both operations are bounded in time.)

-- 
                                      Robert I. Eachus

"As far as I'm concerned, war always means failure." -- Jacques Chirac,
President of France
"As far as France is concerned, you're right." -- Rush Limbaugh