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=0.0 required=3.0 tests=BAYES_40,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.6
X-Received: by 2002:a37:a7d3:: with SMTP id q202mr13841598qke.418.1632120500608;
        Sun, 19 Sep 2021 23:48:20 -0700 (PDT)
X-Received: by 2002:a25:3086:: with SMTP id w128mr30407024ybw.139.1632120500310;
 Sun, 19 Sep 2021 23:48:20 -0700 (PDT)
Path: eternal-september.org!reader02.eternal-september.org!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 19 Sep 2021 23:48:20 -0700 (PDT)
In-Reply-To: <iqqoc7F2lr8U1@mid.individual.net>
Injection-Info: google-groups.googlegroups.com; posting-host=87.88.29.208; posting-account=6yLzewoAAABoisbSsCJH1SPMc9UrfXBH
NNTP-Posting-Host: 87.88.29.208
References: <e3c5c553-4a7f-408a-aaa7-60ec0b70202dn@googlegroups.com>
 <shmnk1$lgf$1@franka.jacob-sparre.dk> <9bc55d72-b90e-45c5-bfd8-cbce565d139dn@googlegroups.com>
 <iqqoc7F2lr8U1@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <44be7c73-f69e-45da-9916-b14a43a05ea3n@googlegroups.com>
Subject: Re: Custom Storage Pool questions
From: Emmanuel Briot <briot.emmanuel@gmail.com>
Injection-Date: Mon, 20 Sep 2021 06:48:20 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:62782
List-Id: <comp.lang.ada>

> > If a compiler is allowed to break up an allocation into multiple 
> > calls to Allocate (and of course Deallocate), how does one go about 
> > enforcing that the user's header is only created once?
> I think one cannot enforce that, because the calls to Allocate do not 
> indicate (with parameters) which set of calls concern the same object 
> allocation. 

I think the only solution would be for this compiler to have another attribute similar to 'Storage_Pool, but that would define the pool for the  descriptor:

    for X'Storage_Pool use Pool;
    for X'Descriptor_Storage_Pool use Other_Pool;

That way the user can decide when to add (or not) extra headers.