Re: Container reqs

[Simon Wright <simon@pushface.org>]

"Ehud Lamm" <mslamm@mscc.huji.ac.il> writes:

> James Rogers <jimmaureenrogers@worldnet.att.net> wrote in message
> news:3BCA173D.FA305845@worldnet.att.net...
> >
> >
> > For the unbounded containers we may want versions allowing one to
> > designate the storage pool used.
> 
> What's the best way to do this?

The BCs now say eg

  with System.Storage_Pools;

  generic
     Storage : in out System.Storage_Pools.Root_Storage_Pool'Class;
  package BC.Containers.Collections.Unbounded is

> Does this mean that we would have to implement useful storage pools as part
> of the effort, and if so - which?

and it seems you can get away with

  with System.Storage_Pools;

  package BC.Support.Standard_Storage is

     type T is access Integer; -- arbitrary subtype

     Pool : System.Storage_Pools.Root_Storage_Pool'Class renames T'Storage_Pool;

  end BC.Support.Standard_Storage;

(ObjectAda & GNAT)


It would be Quite Nice if there were standardised access to the
system's default Storage_Pool, though I can see that if different
types had to be allocated from different pools this might be hard.