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,8e64f4db20d57eb5
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Call by reference vs. call by value
Date: 1996/07/28
Message-ID: <Dv97Ey.MrK@world.std.com>#1/1
X-Deja-AN: 171367157
references: <31F10E50.726@egr.uri.edu>
 <Pine.SUN.3.91.960723082703.22250A-100000@erlang.praxis.co.uk>
 <DuztI8.7EL@world.std.com> <4tdat5$3jb@clams.camtech.com.au>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-07-28T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <4tdat5$3jb@clams.camtech.com.au>,
Peter Morris <peterm@senet.com.au> wrote:
>The occam programming language which I have been using for distributed
>control systems also prohibits aliasing.  As this seems to be a simple
>and efficient way to prevent the problems that aliasing can cause I
>wonder if it might not be a good idea for the full version of ADA95 to
>prohibit aliasing.

SPARK uses a VERY restricted subset of Ada.  Detecting aliasing in full
Ada is neither simple nor efficient.

- Bob