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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a00006d3c4735d70
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-02-04 07:07:20 PST
Path: 
 archiver1.google.com!news2.google.com!news.maxwell.syr.edu!nntp.abs.net!ash.uu.net!spool.news.uu.net!not-for-mail
Date: Wed, 04 Feb 2004 10:07:18 -0500
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: In-Out Parameters for functions
References: <1075390647.405841@master.nyc.kbcfp.com>
 <pan.2004.01.29.18.20.03.61778@email.ro>
 <1075405582.982776@master.nyc.kbcfp.com>
 <s06k109c4nesjr09rhtilrh1ksjsanl6cs@4ax.com>
 <1075482385.142744@master.nyc.kbcfp.com>
 <tk3s10lso10c53841dr3sk5kiok5p46gjf@4ax.com>
 <1075732402.294581@master.nyc.kbcfp.com>
 <loqs105qi5ud0uhet3vbjinlhknmaf4o40@4ax.com>
 <1075741279.952497@master.nyc.kbcfp.com>
 <16nu1099ekujjbpe9dqvs3noi9sdcfja6e@4ax.com>
 <1075817212.745748@master.nyc.kbcfp.com>
 <padv10hc6ndicrrem6beftvnh18gr4f27j@4ax.com>
 <1075824683.769215@master.nyc.kbcfp.com>
 <pan.2004.02.03.22.38.49.622001@email.ro>
 <1075851506.238480@master.nyc.kbcfp.com> <4020C947.81A6D703@0.0>
In-Reply-To: <4020C947.81A6D703@0.0>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Organization: KBC Financial Products
Message-ID: <1075907239.138068@master.nyc.kbcfp.com>
Cache-Post-Path: master.nyc.kbcfp.com!unknown@carrots.nyc.kbcfp.com
X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
NNTP-Posting-Host: 204.253.250.10
X-Trace: 1075907239  10865 204.253.250.10
Xref: archiver1.google.com comp.lang.ada:5229
Date: 2004-02-04T10:07:18-05:00
List-Id: <comp.lang.ada>

Stuart Palin wrote:
 > But, it also creates an opportunity for 'smart compilers' to optimize.

Notice that if an expression has only one possible value regardless of
evaluation order then the compiler can evaluate it in any order it wants,
and with the current evaluation rules, it is unwise to write expressions
that have more than one possible value based on evaluation order. So no
correct existing programs necessarily need to be pessimized by fixing
evaluation order.