From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: String_Access in unbounded string handling? Date: Sun, 14 Jan 2024 16:12:31 +0100 Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sun, 14 Jan 2024 15:12:29 -0000 (UTC) Injection-Info: dont-email.me; posting-host="57e78df867bb3a999590cf71675f1d14"; logging-data="530783"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19DYzP5IOTXoaD5kfaYxTrATBju5QR35Cc=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:87b+1QABYOTvzZw7G9nBiMwOIkQ= Content-Language: en-US In-Reply-To: Xref: news.eternal-september.org comp.lang.ada:65996 List-Id: On 2024-01-14 12:17, Jeffrey R.Carter wrote: > On 2024-01-14 12:05, Blady wrote: >> >> String_Access is defined in A.4.5 Unbounded-Length String Handling: >> 7          type String_Access is access all String; >> >> and note: >> 75  The type String_Access provides a (nonprivate) access type for >> explicit processing of unbounded-length strings. >> >> I wonder what String_Access is for and what could be "explicit >> processing"? > > String_Access is a mistake that should not exist. Well, from one point of view, surely. However I frequently need such a type because I in general refrain from using Unbounded_String. Now, would be no problem to declare it as needed, except for generics! If you have generic packages like: generic type Object_Type (<>) is private; type Object_Access_Type is access all Object_Type; You want all instances to share the same String_Access. So it is conflicting. One is true, it has no place there. It should have been the package Standard or none. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de