From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.5-pre1
Path: eternal-september.org!reader02.eternal-september.org!aioe.org!qkzjKpmJre9K9bE/1pfboA.user.gioia.aioe.org.POSTED!not-for-mail
From: Blady <p.p11@orange.fr>
Newsgroups: comp.lang.ada
Subject: [ANN] UXStrings package available (UXS_20210405).
Date: Sun, 11 Apr 2021 10:45:53 +0200
Organization: Aioe.org NNTP Server
Message-ID: <s4ud01$vm5$1@gioia.aioe.org>
References: <rvr6t4$egd$1@gioia.aioe.org>
 <23472fd3-fe53-4935-84b8-f66a6aa60cfbn@googlegroups.com>
 <s1d2hd$75v$1@gioia.aioe.org> <s20go2$1abe$1@gioia.aioe.org>
NNTP-Posting-Host: qkzjKpmJre9K9bE/1pfboA.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.9.0
Content-Language: en-US
X-Mozilla-News-Host: news://nntp.aioe.org
X-Notice: Filtered by postfilter v. 0.9.2
Xref: reader02.eternal-september.org comp.lang.ada:61769
List-Id: <comp.lang.ada>

Le 06/03/2021 à 19:13, Blady a écrit :
> UXStrings is now available with Alire 
> (https://alire.ada.dev/crates/uxstrings), in your Alire project, just 
> add UXStrings dependency:
> 
> % alr with uxstrings
> 
> Thus you can import the UXStrings package in your programs.

> PS: for French readers, while referencing UXStrings on Alire, I make the 
> opportunity to write a short howto with ALire:
> https://blady.pagesperso-orange.fr/a_savoir.html#alire

Hello,

A second POC implementation for UXStrings is provided. The source code 
files are ending with the number 2 as for instance "uxstrings2.ads".
https://github.com/Blady-Com/UXStrings/blob/master/src/uxstrings2.ads

A GNAT project file "uxstrings2.gpr" is provided with some naming 
conventions for both packages UXStrings  and UXStrings.Text_IO.

Some API have been added to support ASCII 7 bits encoding for both 
version UXStrings 1 and 2. ASCII is a subset of UTF-8 thus no change 
with the internal UTF-8 representation.

However, in addition of UXStrings 1 implementation, the API are now 
aware if content is full ASCII. On one hand, this permits to access 
directly to the position of one character without iterating on UTF-8 
characters. Thus this is a time improvement when content is full ASCII. 
On the other hand, when content is changing the API check if the new 
content is full ASCII. Thus this is a time penalty when changes are not 
full ASCII.

English contents as programming text files are composed of lines in 
majority full ASCII but they may have some line with characters out of 
ASCII set. UXStrings is dealing with both.

Available on GitHub (https://github.com/Blady-Com/UXStrings) and also on 
Alire (https://alire.ada.dev/crates/uxstrings.html).

Feedback is welcome on the actual time improvement on your real use cases.

Thanks, Pascal.