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.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b3edde39ad90f1b7 X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: Representation clauses and streams Date: 2000/01/04 Message-ID: <84tbvi$dm1$1@nnrp1.deja.com>#1/1 X-Deja-AN: 568183077 References: <84du8g$c67$1@nnrp1.deja.com> <386F900C.235952C2@averstar.com> <87k8lq2t4z.fsf@deneb.cygnus.argh.org> X-Http-Proxy: 1.0 x31.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Tue Jan 04 17:51:53 2000 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I) Date: 2000-01-04T00:00:00+00:00 List-Id: In article <87k8lq2t4z.fsf@deneb.cygnus.argh.org>, Florian Weimer wrote: > Since everybody seems to have strong feelings about this issue, I'm > going to ask only one question: Why is IA 13.13.2(17) considered > so important? Even if compilers converge on this specific issue, this > won't give us portable data streams. It might make the stream layout of > similar targets (that is, architecture and compiler combinations) a bit > more similar, but then it doesn't cover the little/big endian problem. > And it doesn't seem to be very helpful when you have to match a given > data format. Your barking up the wrong tree here. This IA is not at all intended to deal with these issues, and indeed it is a good idea if compilers DO address these issues, and they are free to (e.g. the XDR implementation in GNAT). The point is to get reasonably expected behavior for simple binary I/O on a single target (e.g. I stream out a char, I want 8 bits, I stream out an int, I want 32 bits). Sent via Deja.com http://www.deja.com/ Before you buy.