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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,daaf4964abae8ea7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-23 11:30:52 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!news-hog.berkeley.edu!ucberkeley!enews.sgi.com!coop.net!newsfeed1.global.lmco.com!svlnews.lmms.lmco.com!news1.lmtas.lmco.com!not-for-mail From: Gary Scott Newsgroups: comp.lang.ada Subject: Re: Ada And Alternate System Architectures Date: Thu, 23 Aug 2001 13:22:16 -0500 Organization: LM Aeronautics Message-ID: <3B8549D8.A4E3A04A@lmtas.lmco.com> References: <3B8528F1.7B664D21@lmtas.lmco.com> <9m3dcp$9vk$1@nh.pace.co.uk> NNTP-Posting-Host: CAA261517.lmtas.lmco.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {C-UDP; LMTAS} (WinNT; U) X-Accept-Language: en,pdf Xref: archiver1.google.com comp.lang.ada:12354 Date: 2001-08-23T13:22:16-05:00 List-Id: Hi, Thanks. Fortran 95 defines a bit model for integers and then provides intrinsics for manipulating bits within that bit model. What I was wanting was a key word optional argument for bit manipulation intrinsics that allowed me to very slightly modify the bit model by specifying an "endian" (byte) key word. This would allow me to write "portable" code between big/little endian 8-bit byte systems. Apparently if it's only 99.9% portable or acknowledges the existence of a "byte", it can't be considered. I guess I understand, but it seems like this could be addressed through an architecture/system dependent modularized definition. Marin David Condic wrote: > > Ada bends over backwards to avoid specifying anything that would make it > impossible or impractical to implement Ada on just about any platform. For > example, Ada specifies Streams which will most often be implemented as 8-bit > bytes, but the element type is defined in terms of some system defined > storage unit - so it could be 16-bit words or anything else you like. > Similarly, the standard integer types have a minimum range required. For > example, ARM 3.5.4(21) says: > > 21 In an implementation, the range of Integer shall include the > range -2**15+1 .. +2**15-1. > > That would suggest at least 16 bits - but it could be (and often is) 32 > bits. On a PDP-10 it might be 36 bits. > > Ada does exist on processors that aren't 8-bit byte machines. The > Mil-Std-1750a comes immediately to mind. > > MDC > -- > Marin David Condic > Senior Software Engineer > Pace Micro Technology Americas www.pacemicro.com > Enabling the digital revolution > e-Mail: marin.condic@pacemicro.com > Web: http://www.mcondic.com/ > > "Gary Scott" wrote in message > news:3B8528F1.7B664D21@lmtas.lmco.com... > > Hi, > > > > A very naive question...does the Ada standard adequately address > > non-8-bit byte computers? The Fortran language standard committee > > consistently avoids defining anything that relates to a specific > > computer architecture implementation (because what if 6-bit character > > systems one day become common again...). At a very high level, how are > > machine specifics addressed?