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.1 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM,PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no
	version=3.4.4
X-Received: by 2002:ac8:6c26:: with SMTP id k6mr3378487qtu.364.1581699178842;
        Fri, 14 Feb 2020 08:52:58 -0800 (PST)
X-Received: by 2002:aca:f10:: with SMTP id 16mr2406370oip.117.1581699178555;
 Fri, 14 Feb 2020 08:52:58 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Fri, 14 Feb 2020 08:52:57 -0800 (PST)
In-Reply-To: <2a19cdb1-6f01-4b1d-8597-b6ee21ed60ed@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=146.5.2.231;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 146.5.2.231
References: <2a19cdb1-6f01-4b1d-8597-b6ee21ed60ed@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5287ee89-29ca-4c88-8b0b-c307e1933716@googlegroups.com>
Subject: Re: Simple Data Endianness
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Fri, 14 Feb 2020 16:52:58 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:58070
Date: 2020-02-14T08:52:57-08:00
List-Id: <comp.lang.ada>

On Thursday, February 13, 2020 at 2:42:14 AM UTC-7, guijarroc...@gmail.com =
wrote:
> Hi,=20
>=20
>=20
> The problem I present today is related to the coexistence between big-end=
ian and little-endian application data.

I think this depends on the use-case of the software. If everything is goin=
g to be Ada, I think all you need is to DSA things. -- See: https://video.f=
osdem.org/2020/AW1.125/ada_distribution.webm

You can also configure PolyORB to be both DSA and CORBA, IIRC. So, even if =
you can't directly distribute to the various architectures (which I would b=
e surprised about) you *could* let CORBA handle the remote-calls/translatio=
ns if you are going to use this with extant non-Ada software (assuming that=
 there's an easily integrable CORBA there).

But if this is integrating new Ada into already extant [distributed] system=
s, you should take a look at how they're handling the communications. If it=
's something like UDP then your best bet is probably to go in and create th=
e custom datagram packets yourself, if it's ASN.1 based communications then=
 [IIRC] you can use this: https://www.thanassis.space/asn1.html

----
There's also the boring case of "reading/writing a binary file" -- if this =
is the case then you could probably do things via these representation clau=
ses and stream attributes.