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,9a586954b11ae008
X-Google-Attributes: gid103376,public
From: mazzanti@iei.pi.cnr.it (Franco Mazzanti)
Subject: Re: What Happened While I Wasn't Looking?
Date: 1997/04/09
Message-ID: <mazzanti-0904971843290001@131.114.200.115>#1/1
X-Deja-AN: 231837273
Organization: IEI-CNR
Newsgroups: comp.lang.ada
Date: 1997-04-09T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert A Duff wrote:

> >     I'm impressed.  Apparently 13.3(13) can be read to say: If an ad-
> >dress clause causes a bad effect, then the specified address was invalid 
> >and the program is erroneous.  I certainly don't get any comfort out of 
> >such a flexible reading.
> 
> Well, I think 13.3(13) is pretty broad.  It allows the implementation a
> lot of freedom in declaring things erroneous.  ...
> 
> - Bob


13.3(13) also allows the implementation a lot of freedom in not declaring
anything. 

There is no "documentation requirement" nor any "implementation advice"
suggesting implementation to give some advice about when an address is 
valid or not. Still the responsibility on the erroneousness of the code 
is given totally the programmer.

Franco Mazzanti
(mazzanti@iei.pi.cnr.it)