From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Exclusive file access Date: Tue, 1 Sep 2015 09:33:42 +0200 Organization: cbb software GmbH Message-ID: References: <75714e3f-c047-413d-9aa5-3ff423167863@googlegroups.com> <1440837116.20971.33.camel@obry.net> <87oahpovpn.fsf@mid.deneb.enyo.de> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: jSS3it0g+GyWYSMU5pi+5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:27666 Date: 2015-09-01T09:33:42+02:00 List-Id: On Mon, 31 Aug 2015 18:34:12 -0500, Randy Brukardt wrote: > "Dmitry A. Kazakov" wrote in message > news:mvil865iebyb$.1of2shk5faacq$.dlg@40tude.net... > ... >>> As long as you don't use Wide_String—if you do use that, things get >>> rather messy. >> >> Both are messy. Character and Ada.Text_IO was designed prior to Unicode. >> Later amendments were futile attempts to repair what needed no repair. > > I would have said: "Later amendments were futile attempts to repair what > needed replacement." since we have no choice but to support modern character > sets in Ada. But the way to do that isn't by abandoning strong typing > (Ada.Strings.UTF_Encoding) or by duplicating everything many times > (Wide_Wide_String, which naturally leads to Wide_Wide_Text_IO which leads to > Wide_Wide_Open which leads to Wide_Wide_Madness). Agreed > Since a sensible solution can't be done compatibility, we needed to start > over -- but that's never had appropriate traction. And good so, because without reworking the type system no reasonable solution is impossible. Either: a. Encoding must be an interface, a view, of the string type decoupled from its internal representation. b. If the representation is the encoding, then the interface of an array of characters must still be available. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de