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 X-Google-Thread: 103376,5bcc293dc5642650 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.8.199 with SMTP id t7mr2176044pba.3.1319265634800; Fri, 21 Oct 2011 23:40:34 -0700 (PDT) Path: d5ni42394pbc.0!nntp.google.com!news2.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Michael Rohan Newsgroups: comp.lang.ada Subject: Re: Why no Ada.Wide_Directories? Date: Fri, 21 Oct 2011 23:32:44 -0700 (PDT) Organization: http://groups.google.com Message-ID: <20586225.484.1319265164765.JavaMail.geo-discussion-forums@prgt10> References: <9937871.172.1318575525468.JavaMail.geo-discussion-forums@prib32> <418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com> Reply-To: comp.lang.ada@googlegroups.com NNTP-Posting-Host: 76.126.190.57 Mime-Version: 1.0 X-Trace: posting.google.com 1319265634 26509 127.0.0.1 (22 Oct 2011 06:40:34 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 22 Oct 2011 06:40:34 +0000 (UTC) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.126.190.57; posting-account=1YPeQwoAAACAk-xhKPD32B0GIDdsFFtk User-Agent: G2/1.0 X-Google-Web-Client: true Xref: news2.google.com comp.lang.ada:14143 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2011-10-21T23:32:44-07:00 List-Id: Hi, There seems to be two major issues being considered here * The handling of "string" data with within Ada applications, i.e., should = String be opaque with, perhaps, class type interfaces giving views into thi= s data as Latin-1, UTF8, UCS-2, etc. * The more immediate issue I raised initially, what to do when you have a W= ide_String and want to use it as a file name. I'm currently just convertin= g such names to UTF8 which works well on Linux but probably will have issue= on Windows if I were to use non-Latin-1 type strings. While the first issue is relatively involved, the second issue could be han= dled by the run-time (with the possibilities of exceptions if the name coul= d not be mapped, but that would be up to the application to handle). My initial question suggested there should be Wide_* versions of the packag= es that interface with the OS (Directories, Command_Line, Environment_Varia= bles, etc). Having implemented wrappers for these it seems to me extending= the existing packages to have additional routines for Wide_String/Wide_Wid= e_String would be cleaner. This extension of the existing packages would be something that might be po= ssible to consider for the next revision (but maybe too late?). Take care, Michael.