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,1054df2e2c490eda
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Q: Memory management
Date: 1996/07/17
Message-ID: <dewar.837645491@schonberg>#1/1
X-Deja-AN: 168684209
references: <uvvg27kjm35.fsf@chaq.informatik.uni-tuebingen.de>
 <DtKt46.AJ9.0.-s@inmet.camb.inmet.com> <Dtzv4J.9FL@thomsoft.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-07-17T00:00:00+00:00
List-Id: <comp.lang.ada>


"Be aware that this is only implementation advice.  I presume that all
compilers will follow it.  Why wasn't this made a hard requirement?"

(addresses pointing at first component of array)

The reason this was not made a hard requirement is that you really can't
make any formal statements about such matters. What does it mean for
an address to "point to" anything?

Also, there may be architectures in which this requirement would be a
burden.