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=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,de41c0d7c45160c8
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-03-07 06:06:23 PST
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!math.ohio-state.edu!uwm.edu!news.alpha.net!news.mathworks.com!panix!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody
From: dewar@cs.nyu.edu (Robert Dewar)
Newsgroups: comp.lang.ada
Subject: Re: Pointers
Date: 7 Mar 1995 07:20:22 -0500
Organization: Courant Institute of Mathematical Sciences
Message-ID: <3jhj26$2er@gnat.cs.nyu.edu>
References: <794482546snz@jonf.demon.co.uk>
NNTP-Posting-Host: gnat.cs.nyu.edu
Date: 1995-03-07T07:20:22-05:00
List-Id: <comp.lang.ada>

Jon, we have to ask why a simple address clause

   for x use at ...

does not work for you, since this is the obvious way of reading a specific
memory address. You have to consult your implementor on how to represent
address values, since this is obviously target dependent.