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=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a37:447:: with SMTP id 68mr452510qke.449.1581606757177; Thu, 13 Feb 2020 07:12:37 -0800 (PST) X-Received: by 2002:a05:6830:194:: with SMTP id q20mr14169296ota.92.1581606756720; Thu, 13 Feb 2020 07:12:36 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!aioe.org!peer01.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 13 Feb 2020 07:12:36 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: google-groups.googlegroups.com; posting-host=47.185.239.228; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.239.228 References: <2a19cdb1-6f01-4b1d-8597-b6ee21ed60ed@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Simple Data Endianness From: Optikos Injection-Date: Thu, 13 Feb 2020 15:12:37 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 2730 X-Received-Body-CRC: 1899531334 Xref: reader01.eternal-september.org comp.lang.ada:58045 Date: 2020-02-13T07:12:36-08:00 List-Id: On Thursday, February 13, 2020 at 5:10:44 AM UTC-6, Dmitry A. Kazakov wrote= : > On 2020-02-13 10:42, guijarrockGuijarro wrote: >=20 > > The problem I present today is related to the coexistence between big-e= ndian and little-endian application data. >=20 > How low-level representation aspect might be relevant to application data= ? If the exchange of app data between 2 or more computers is word-wise binary= instead of byte-wise textual, such as via binary-formatted files or via bi= nary-formatted datagrams/byte-streams as payload of networking protocols. > > type Colour is (BLACK,YELLOW,WHITE,RED); > > for Colour'SIZE use 32; > >=20 > > Is there any analogous way of doing this as in the case of compound typ= es? >=20 > Should it include middle-endian packed binary-coded decimals with memory= =20 > parity bits? (:-)) middle-endian: Yes, if porting to PDP11, Honeywell 316, and the like. ;^) parity bits: Yes, if porting to Prime 50 series that had mark-parity ASCII= characters 128 to 255 packed 2 at a time into 16-bit bytes. ;^) BCD: Yes, if the app data was written to a file in BCD, such as easily so b= y a BCD capable language (e.g., COBOL, Ada). This one is less of a joke, b= ecause these COBOL-written app-data files are commonplace on IBM mainframes= , especially if the new work is Ada on non-mainframes reading in the data d= ownloaded from mainframes.