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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,73cb216d191f0fef X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII X-Received: by 10.180.11.239 with SMTP id t15mr108248wib.5.1366082679453; Mon, 15 Apr 2013 20:24:39 -0700 (PDT) Path: hg5ni6325wib.1!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.103.MISMATCH!feeder3.cambriumusenet.nl!feed.tweaknews.nl!216.196.110.144.MISMATCH!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!news.teledata-fn.de!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!news.uni-weimar.de!medsec1.medien.uni-weimar.de!lucks From: Stefan.Lucks@uni-weimar.de Newsgroups: comp.lang.ada Subject: Re: Is this expected behavior or not Date: Mon, 8 Apr 2013 09:48:07 +0200 Organization: Bauhaus-Universitaet Weimar Message-ID: References: <1gnmajx2fdjju.1bo28xwmzt1nr.dlg@40tude.net> <3gv2jwc95otm.pl2aahsh9ox8.dlg@40tude.net> <1gkxiwepaxvtt$.u3ly33rbwthf.dlg@40tude.net> <1fmcdkj58brky.bjedt0pr39cd$.dlg@40tude.net> <1bj564vat3q1j$.1s4d00rlzx4ux$.dlg@40tude.net> <4hzv51v872q2$.1imijbwd7heqm$.dlg@40tude.net> <1htu9idmcci7x.1vr9eafeivqah$.dlg@40tude.net> NNTP-Posting-Host: medsec1.medien.uni-weimar.de Mime-Version: 1.0 X-Trace: tigger.scc.uni-weimar.de 1365407362 22957 141.54.178.228 (8 Apr 2013 07:49:22 GMT) X-Complaints-To: news@tigger.scc.uni-weimar.de NNTP-Posting-Date: Mon, 8 Apr 2013 07:49:22 +0000 (UTC) X-X-Sender: lucks@debian In-Reply-To: <1htu9idmcci7x.1vr9eafeivqah$.dlg@40tude.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Date: 2013-04-08T09:48:07+02:00 List-Id: On Sun, 7 Apr 2013, Dmitry A. Kazakov wrote: >> If you have mounted different filesystems using different encodings on >> your system, how on earth should Ada.Text_IO even "know" which encoding = to >> apply? > > How is this relevant to the issue that encoding must a part of the type? Because even if the implementation of Ada.Text_IO.Open would know the=20 encoding of the filename, it could do nothing useful with it. >> Yes, this is C-esque of the worst kine. However, what would you expect >> when making system calls with operation systems written in C? > > I expect the type system to handle equivalent types of different > representations such as UTF-8 and UCS-4 strings. As it already does in th= e > case Universal_Integer vs. Integer. Both are distinct types, both have > different representations, both are considered equivalent in certain case= s. Universal_Integer is a pseudo-type. You cannot define an object O:=20 Universal_Integer, neither a function returning Universal_Integer ... The only thing that Universal_Integer handles well is a neat way of=20 defining constants. The mess with the different string types in Ada is not= =20 just about string constants, it goes much beyond. ------ I love the taste of Cryptanalysis in the morning! ------ --Stefan.Lucks (at) uni-weimar.de, Bauhaus-Universit=E4t Weimar, Germany--