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=-0.9 required=3.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.5-pre1 Path: eternal-september.org!reader02.eternal-september.org!aioe.org!news.mixmin.net!gandalf.srv.welterde.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Ada and Unicode Date: Tue, 20 Apr 2021 14:13:30 -0500 Organization: JSA Research & Innovation Message-ID: References: <607b5b20$0$27442$426a74cc@news.free.fr> <86mttuk5f0.fsf@stephe-leake.org> Injection-Date: Tue, 20 Apr 2021 19:13:31 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="12948"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:61870 List-Id: "J-P. Rosen" wrote in message news:s5k0ai$bb5$1@dont-email.me... > Le 19/04/2021 à 15:00, Luke A. Guest a écrit : >> They're different types and should be incompatible, because, well, they >> are. What does Ada have that allows for this that other languages >> doesn't? Oh yeah! Types! > > They are not so different. For example, you may read the first line of a > file in a string, then discover that it starts with a BOM, and thus decide > it is UTF-8. > > BTW, the very first version of this AI had different types, but the ARG > felt that it would just complicate the interface for the sake of abusive > "purity". Unfortunately, that was the first instance that showed the beginning of the end for Ada. If I remember correctly (and I may not ;-), that came from some people who were wedded to the Linux model where nothing is checked (or IMHO, typed). For them, a String is simply a bucket of octets. That prevented putting an encoding of any sort of any type on file names ("it should just work on Linux, that's what people expect"). The rest follows from that. Those of us who care about strong typing were disgusted, the result essentially does not work on Windows or MacOS (which do check the content of file names - as you can see in GNAT compiling units with non-Latin-1 characters in their names), and I don't really expect any recovery from that. Randy.