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-01-27 11:31:41 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: Tue, 27 Jan 2004 14:31:24 -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: <wcczncdrowb.fsf@shell01.TheWorld.com>
 <mailman.15.1075065014.2270.comp.lang.ada@ada-france.org>
 <wcc8yju2tjk.fsf@shell01.TheWorld.com>
 <1075159458.149886@master.nyc.kbcfp.com>
 <wcc4qui2sec.fsf@shell01.TheWorld.com>
 <d%jRb.1212$nR.528@nwrdny01.gnilink.net>
 <mailman.35.1075191506.2270.comp.lang.ada@ada-france.org>
 <1075225041.167448@master.nyc.kbcfp.com>
 <pan.2004.01.27.18.41.28.388988@email.ro>
In-Reply-To: <pan.2004.01.27.18.41.28.388988@email.ro>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Organization: KBC Financial Products
Message-ID: <1075231885.317219@master.nyc.kbcfp.com>
Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com
X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
NNTP-Posting-Host: 204.253.250.10
X-Trace: 1075231885  7113 204.253.250.10
Xref: archiver1.google.com comp.lang.ada:4924
Date: 2004-01-27T14:31:24-05:00
List-Id: <comp.lang.ada>

David Starner wrote:
> It would quite a bit of work to prove that two functions don't have side
> effects, especially in the face of exceptions. It could easily call for
> intra-unit optimizations, and many cases just won't be possible.

That's fine. In those cases the compiler is obviously not going to
choose evaluation order based on efficiency, so specifying the order
will not pessimize the code.

> Ada usually discourages tight hidden coupling

How does it do that, aside from forbidding functions to have
*out parameters?