Re: Status of AdaCL: Ada Class Library

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

Randy Brukardt schrieb:
> Am 22.02.2010, 02:51 Uhr, schrieb Bj�rn Persson <bjorn@rombobj�rn.se>:
> 
>> I had intended to switch from Charles to Ada.Containers, but I changed my
>> mind when I learned that Ada.Containers can't even be read by multiple
>  > tasks at once.

> It's easy to wrap container operations in a protected object, and that is 
> always allowed (such operations are not potentially blocking). That allows 
> tailoring the locking for the actual usage, and even hiding the actual 
> container to prevent abuse.

Indeed, arent' there advantages in hiding data stores like
Ada.Containers behind some facade, whether the use is
sequential or not: everything else always smells of
exposed internal data structures, or lack of abstraction.
There need to be good reasons for using List, Set, etc.
as is, I think. Just like there should be good reasons
to expose arrays.