Re: Allocators design flaw

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2017-10-14 17:17, Victor Porton wrote:
> Dmitry A. Kazakov wrote:
> 
>> On 2017-10-14 16:24, Victor Porton wrote:
>>
>>> I mean, it is because we cannot change C standard for better
>>> compatibility with Ada. But we can change Ada 202x for better
>>> compatibility with C libraries.
>>
>> There is nothing incompatible in what you described.
>>
>> There are many C libraries (most?) which cannot deal with objects
>> allocated outside, e.g. in an Ada pool. There was never a big problem to
>> communicate with such libraries.
> 
> I want to create an Ada pool which does the same (de)allocation as a C
> library.
> 
> The problem is that creating such a pool is (seemingly) impossible with
> current Ada RM.

It is possible as I explained. You allocate additional information in 
front of the object and shift address. Upon deallocation you use that 
information to shift the address back before passing it to C's free. The 
same technique is used when handling Ada's array address issue in Simple 
Components.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de