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!RKN7TKnHC01q0gdg6EhkbQ.user.46.165.242.75.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: On absurdity of collections 7.6.1 (11.1/3) Date: Wed, 29 Sep 2021 12:05:22 +0100 Organization: Aioe.org NNTP Server Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: gioia.aioe.org; logging-data="58257"; posting-host="RKN7TKnHC01q0gdg6EhkbQ.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (darwin) X-Notice: Filtered by postfilter v. 0.9.2 Cancel-Lock: sha1:roAeLG6i9rHNat+9H1KAsPmoRws= Xref: reader02.eternal-september.org comp.lang.ada:62863 List-Id: "Dmitry A. Kazakov" writes: > type Item_Ptr is access all Item; > function New_Item > ( Pool : in out Root_Storage_Pool'Class; > Text : String > ) return Item_Ptr; What I don't see is how you can implement this, never mind any other problems. 13.11(17) says "If Storage_Pool is not specified for a type defined by an access_to_object_definition, then the implementation chooses a standard storage pool for it in an implementation-defined manner." I see that 3.10(8) says "Access-to-object types are further subdivided into pool-specific access types [...] and general access types, whose values can designate the elements of any storage pool [...]" which implies that there *is* a mechanism.