Re: little precision about anonymous access types

["Randy Brukardt" <randy@rrsoftware.com>]

The better solution here is restriction No_Anonymous_Allocators (see 
H.4(8.1/3)). Using that restriction helps because it forces all allocation 
to named access types (for which you can do deallocation in all of the 
normal ways). This is just to note that Ada does have ways to mitigate this 
problem (I noted another one, pragma Default_Storage_Pool, in a previous 
message). The annoyance is that these things aren't the default.

                   Randy.


"Mehdi Saada" <00120260a@gmail.com> wrote in message 
news:1fbd0763-bed4-49f5-a1c8-51a634e89eb2@googlegroups.com...
I may add, that the craziest thing was to allow the very possibly of using 
allocators with non-discriminant/non-parameter anonymous access (though I 
have no idea, and it's not easy to find, where and for how long goes things 
like values like my_func(new something', ...) types. Their existence, that 
forbid and uselessness aside, it wouldn't be that much of a loophole. At 
least provide a way to bind the objects' life time to something, dudes...