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-Thread: 103376,b3f788f59498d3af
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!club-internet.fr!feedme-small.clubint.net!news.mixmin.net!news2.arglkargh.de!noris.net!storethat.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: Exceptions and out procedure arguments (using GNAT GPL)
From: Georg Bauhaus <rm.tsoh+bauhaus@maps.futureapps.de>
In-Reply-To: <1mhmyqf4l1lzn$.42eeylu5yrjk.dlg@40tude.net>
References: <79c673pq5htg508nkoi935n3udqg5ps7r8@4ax.com>
	 <1182181497.595409.300500@a26g2000pre.googlegroups.com>
	 <drle731ukcmhlt5km966imoudr5s92napd@4ax.com>
	 <1182238493.512406.168820@o61g2000hsh.googlegroups.com>
	 <1182266486.650797.262430@a26g2000pre.googlegroups.com>
	 <u1ofbjnyd74k$.9604oalmbm4q$.dlg@40tude.net>
	 <4678c6a0$0$23135$9b4e6d93@newsspool1.arcor-online.net>
	 <1o6rnwgzezcr2$.mv31ct5mmmso$.dlg@40tude.net>
	 <1182329193.7759.30.camel@kartoffel>
	 <f9r2vckevf2w.ym9pgqu88b03$.dlg@40tude.net>
	 <1182334409.7759.39.camel@kartoffel>
	 <1mhmyqf4l1lzn$.42eeylu5yrjk.dlg@40tude.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1182349018.7759.51.camel@kartoffel>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Date: Wed, 20 Jun 2007 16:16:58 +0200
Organization: Arcor
NNTP-Posting-Date: 20 Jun 2007 16:16:54 CEST
NNTP-Posting-Host: 2c660b71.newsspool2.arcor-online.net
X-Trace: 
 DXC=O^_^6lA;oe]@@RW1FjIB5SA9EHlD;3YcR4Fo<]lROoRQ8kF<OcfhCO[S<icOlOl>4^=kbmW`a1fGWC`2T@AUZfC[VfF1K_J1ZJP
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:16271
Date: 2007-06-20T16:16:54+02:00
List-Id: <comp.lang.ada>

On Wed, 2007-06-20 at 14:58 +0200, Dmitry A. Kazakov wrote:
> On Wed, 20 Jun 2007 12:13:29 +0200, Georg Bauhaus wrote:
> 
> > On Wed, 2007-06-20 at 11:29 +0200, Dmitry A. Kazakov wrote:
> >> On Wed, 20 Jun 2007 10:46:33 +0200, Georg Bauhaus wrote:
> >> 
> >>>>> And can you document all side effects on by reference (or global)
> >>>>> variables at all, in the presence of exceptions?
> >>>> 
> >>>> That depends on the meaning of "all." Certainly, we cannot control
> >>>> side-effects on the CPU's cache or on the green gas emission caused by
> >>>> consuming electricity during subprogram execution...
> >>> 
> >>> Yes, no need repeating the absurd. So what is the meaning of "all
> >>> side effects"?
> >> 
> >> Language-distinguishable sets of program states corresponding the
> >> identified elements of the problem space.
> > 
> > Rephrasing the notion won't help defining it.
> 
> OK, give your definition of [side] effect of program execution so that we
> could discuss your point.

A side effect of a subprogram P is a possible update of an object
(in some partition) that is not mentioned in P's parameter profile.