From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.6
Path: eternal-september.org!reader02.eternal-september.org!aioe.org!Hx95GBhnJb0Xc8StPhH8AA.user.46.165.242.91.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Custom Storage Pool questions
Date: Fri, 17 Sep 2021 22:39:05 +0200
Organization: Aioe.org NNTP Server
Message-ID: <si2ud7$fv2$1@gioia.aioe.org>
References: <e3c5c553-4a7f-408a-aaa7-60ec0b70202dn@googlegroups.com>
 <ly5yv1bxgy.fsf@pushface.org> <shtg99$tgd$1@gioia.aioe.org>
 <lywnnha7y1.fsf@pushface.org>
 <1d2551f4-8189-44ec-a54d-4a56a672bedcn@googlegroups.com>
 <c2d59417-398f-42a0-ab4b-b4f947325be0n@googlegroups.com>
 <si26q3$13l1$1@gioia.aioe.org> <lyo88r9e99.fsf@pushface.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="16354"; posting-host="Hx95GBhnJb0Xc8StPhH8AA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
Content-Language: en-US
X-Notice: Filtered by postfilter v. 0.9.2
Xref: reader02.eternal-september.org comp.lang.ada:62767
List-Id: <comp.lang.ada>

On 2021-09-17 21:46, Simon Wright wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> 
>> Nope, especially because the issue with X'Address being unusable for
>> memory pool developers is a long standing painful problem that need to
>> be resolved. That will never happen until a measurable group of people
>> start asking questions. So you are doubly welcome.
> 
> There are two attributes that we should all have known about,
> Descriptor_Size[1] (bits, introduced in 2011) and Finalization_Size[2]
> (storage units, I think, introduced in 2017)

They are non-standard and have murky semantics I doubt anybody really 
cares about.

What is needed is the address passed to Deallocate should the object be 
freed = the address returned by Allocate. Is that too much to ask?

BTW, finalization lists (#2) should have been removed from the language 
long ago. They have absolutely no use, except maybe for debugging, and 
introduce huge overhead. The semantics should have been either 
Unchecked_Deallocation or compiler allocated objects/components may call 
Finalize, nothing else.

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