From: Tucker Taft <tucker.taft@gmail.com>
Subject: Re: String_Access in unbounded string handling?
Date: Wed, 17 Jan 2024 05:34:12 -0800 (PST) [thread overview]
Message-ID: <afd791fa-853f-48fa-9223-759b12d4ed87n@googlegroups.com> (raw)
In-Reply-To: <uo0f65$dlcm$1@dont-email.me>
On Sunday, January 14, 2024 at 6:05:45 AM UTC-5, Blady wrote:
> Hello,
>
> 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"?
The idea was to support the explicit use of new String'(...), X.all, and Unchecked_Deallocation rather than the implicit use of the heap inherent in Unbounded strings. It was recognized that you need a single global access type to avoid having to do conversions all over the place. This predated the availability of stand-alone objects of an anonymous access type (aka "SAOOAAATs" ;-), but those are not universally loved either. It certainly cannot be removed now without potentially very painful disruption of existing users. It could be moved to a different package without too much disruption, but I haven't seen any groundswell of interest in doing that either.
>
> Thanks, Pascal.
Take care,
-Tuck
next prev parent reply other threads:[~2024-01-17 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 11:05 String_Access in unbounded string handling? Blady
2024-01-14 11:17 ` Jeffrey R.Carter
2024-01-14 15:12 ` Dmitry A. Kazakov
2024-01-17 1:30 ` Randy Brukardt
2024-01-17 1:24 ` Randy Brukardt
2024-01-17 9:54 ` Blady
2024-01-17 13:34 ` Tucker Taft [this message]
2024-01-19 1:36 ` Randy Brukardt
2024-01-30 15:53 ` Blady
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox