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
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3db17e1869f3a33d
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Ada95 Streams Question
Date: 1996/06/30
Message-ID: <dewar.836136307@schonberg>#1/1
X-Deja-AN: 162980957
references: <9606232338.AA12517@nile.gnat.com>
 <4qlshm$1j9e@info4.rus.uni-stuttgart.de> <dewar.835633090@schonberg>
 <DtprD2.MnF@world.std.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-30T00:00:00+00:00
List-Id: <comp.lang.ada>


Bob Duff said

"    2. Solving the problem of heterogeneous is beyond the scope of the
       annex, but we don't want to get in the way of supporting
       heterogeneous systems.  We hope compiler writers will address
       those issues, and who knows, maybe that support will become
       standard someday.  Thus, the DS annex should not do anything that
       *prevents* its use in heterogeneous systems."

In fact there is nothing in the annex that is in any way relevant to the
homgenous vs hetergenous distribution issue, except for the recommendation
that the default stream representation of primitive data types correspond
to their memory representation, and that is only a recommendation, which
is simply clearly inappropriate for a hetergenous implementation (the
whole point of implementation advice is that it is advice, you ignore it
if it is inappropriate to your implementation).

Sure there are additional implementation problems to be solved in the
hetergenous case, but these are implementation issues, not language issues.