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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,c689b55786a9f2bd X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Path: g2news2.google.com!news3.google.com!feeder.news-service.com!feeds.phibee-telecom.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!gegeweb.org!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: for S'Image use Func?? Date: Tue, 11 May 2010 20:57:18 +0200 Organization: Ada At Home Message-ID: References: <4be417b4$0$6992$9b4e6d93@newsspool4.arcor-online.net> <1qcb6z4i20dyb.1dz2hd4c0vx69.dlg@40tude.net> NNTP-Posting-Host: EFpv4lnpRyjbMhM0po550g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/10.53 (Win32) Xref: g2news2.google.com comp.lang.ada:11523 Date: 2010-05-11T20:57:18+02:00 List-Id: Le Tue, 11 May 2010 19:17:38 +0200, Warren a =C3=A9cr= it: > All this is well and good for applications that can work in > "implementation defined" units of type Stream_Element. =E2=80=9CImplementation defined=E2=80=9D here, means =E2=80=9Cplatform d= ependent=E2=80=9D. This is not = =E2=80=9Ccompiler implementation dependent=E2=80=9D, this is =E2=80=9Cpl= atform implementation = dependent=E2=80=9D. So this is not Ada's fault, nor this one or that one= compiler = implementation, this is just the real world. If you real world is never something else than file storage element of 8= = bits, then the Assert pragma will never fail and that's all (you will ev= en = do not need the this Assert pragma at all, which is for greater = trustability) > A pragma > won't fix the problem No language will fix the problem if you need a 8 bits file storage eleme= nt = on a platform which uses something else. > should it be different than a byte. Granted, > it will never likely come up on the platforms I have in mind. So, what' wrong ? > But I do believe a POSIX friendly version of this should exist. > Then the entire issue goes away. Under the hood, if the types work > out the to the same size as a byte, you can capitalize on that > in an implementation dependendant way. > > Anything that makes Ada more posix friendly, helps its general > acceptance. Ada is POSIX friendly, and there are POSIX bindings to Ada, as well as a= n = ISO standard for the POSIX Ada binding. You are formally wrong when you = = suggest Ada is not POSIX friendly. Ada will simply not be able to be POSIX friendly on platforms which are = = not POSIX. You know... even Windows XP Pro is very fat to be POSIX compliant ;) (to= = not talk about prior version of Windows) -- = pragma Asset ? Is that true ? Waaww... great