Re: Allocators design flaw

[Simon Wright <simon@pushface.org>]

Victor Porton <porton@narod.ru> writes:

> As far as I understand, it will not work, because the C library I am
> writing bindings for may try to free an object allocated by me (or I
> my need to free an object allocated by the library).

This vital info wasn't part of your original problem statement.

I suppose you might just get away with creating a storage pool backed up
by raptor_alloc_memory() (and corresponding free). But you'd have to
cope with the alignment issue as Dmitry has suggested.

Is the Ada side meant to understand things allocated on the C side? If
so, you'll need to specify the representation exactly.

Is the C side meant to understand things allocated on the Ada side?
Likewise (and no room for hidden dope vectors!)