From: Vincent DIEMUNSCH <vincent.diemunsch@gmail.com>
Subject: Re: When to use Bounded_String?
Date: Thu, 28 Dec 2017 03:46:55 -0800 (PST)
Date: 2017-12-28T03:46:55-08:00 [thread overview]
Message-ID: <96764e4c-48df-4042-845e-12341149bc87@googlegroups.com> (raw)
In-Reply-To: <0cc30dc8-4528-4e5c-91dd-24dfbe3cbcb2@googlegroups.com>
Le jeudi 23 novembre 2017 11:04:12 UTC+1, briot.e...@gmail.com a écrit :
> You could use GNATCOLL.Strings, which provide the short-string-optimization:
> when a string is shorter than 19 or 23 characters (32 bit and 64 bit systems) then
> no allocation takes place.
> They also provide a much larger number of operations than standard strings or
> unbounded_strings, are task safe, and handle unicode.
Yes, they are really a great improvement. But they would be perfect if :
1. they handled UTF-8 as the de-facto standard encoding, for strings.
2. they could see strings as sequences of 32-bits Unicode Code Points (Wide_Wide_Characters).
next prev parent reply other threads:[~2017-12-28 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 2:19 When to use Bounded_String? Victor Porton
2017-11-19 9:55 ` Niklas Holsti
2017-11-20 5:38 ` J-P. Rosen
2017-11-20 7:32 ` Niklas Holsti
2017-11-23 10:04 ` briot.emmanuel
2017-12-28 11:46 ` Vincent DIEMUNSCH [this message]
2017-12-28 12:00 ` Dmitry A. Kazakov
2017-12-28 12:29 ` Mehdi Saada
2017-12-29 0:42 ` Randy Brukardt
2017-12-29 9:11 ` Simon Wright
2017-12-28 14:28 ` vincent.diemunsch
2017-12-29 0:36 ` Randy Brukardt
2017-12-29 8:48 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox