Re: Flexible Strings (was Equality operator...)

[mheaney@ni.net (Matthew Heaney)]

In article
<53F35740C6EF076C.14BEEF8227919F71.39E2B6FED1F30314@library-proxy.airnews.ne
t>, clines@delete_this.airmail.net (Kevin Cline) wrote:

>Perhaps there is not a lot of
>difference in theory between Ada and C storage management, but there is a huge
>practical difference.  In C or C++, the application programmer can take
>complete control of the allocation process in a couple of ways.  In C++, new
>and delete can be redefined globally or on a class-by-class basis.
>Additionally, the compiler vendor's implementation of malloc and free can be 
>replaced with one more carefully tuned to the particular application.
>Although not mandated by the standard, almost all C compilers do link malloc
>and free from their run-time library, and replacement implementations can be
>linked instead.  Few Ada compilation systems are so open.

I'm confused.  Isn't that what storage pools are for in Ada 95?  I can
create a pool so that new and Unchecked_Deallocation call routines I
define, on a type-by-type basis.  What's the difference?

--------------------------------------------------------------------
Matthew Heaney
Software Development Consultant
<mailto:matthew_heaney@acm.org>
(818) 985-1271