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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.ada Subject: Re: AI12-0218: What is the portable representation clause for processing IETF packets on little-endian machines? Date: Thu, 10 May 2018 16:14:55 -0700 Organization: A noiseless patient Spider Message-ID: <87lgcryufk.fsf@nightsong.com> References: <9af47760-e731-4cb5-a1a0-d63e31019ce5@googlegroups.com> <877eob1cc6.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="8ee8a87c586ad688bbbd7b3afaf6ee4e"; logging-data="28373"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18nOO8XfWcLBfGv80Nx1i+/" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Cancel-Lock: sha1:+uu6dNyZZTLK/g0Mat78c5USBEk= sha1:AMnh76gKDK+T5sFvHLAC+/WJOg0= Xref: reader02.eternal-september.org comp.lang.ada:52229 Date: 2018-05-10T16:14:55-07:00 List-Id: Niklas Holsti writes: > It is not clearly explained how endianness is interpreted for fields > that do not align with octet boundaries. I don't see an unclarity as long as the machine is either big or little endian. That specifies whether the more significant bits are at the higher addresses or the lower ones. There could possibly be some confusion with the weird old VAX representation that was neither big nor little, but the Erlang page doesn't try to deal with that case.