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,a00006d3c4735d70 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-27 01:23:49 PST Path: archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!62.173.119.178!not-for-mail From: Peter Amey Newsgroups: comp.lang.ada Subject: Re: In-Out Parameters for functions Date: Tue, 27 Jan 2004 09:23:42 +0000 Message-ID: References: <5ad0dd8a.0401240721.7682f2e1@posting.google.com> NNTP-Posting-Host: 62.173.119.178 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de 1075195427 25588579 62.173.119.178 ([69815]) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en In-Reply-To: Xref: archiver1.google.com comp.lang.ada:4889 Date: 2004-01-27T09:23:42+00:00 List-Id: Interesting sub thread. It has raised all the nastiness of function side effects, evaluation order dependency and aliasing. FWIW, avoiding these kinds of issue were a major motivator in the design of SPARK. SPARK functions never have side effects, the language is free from evaluation order dependencies and aliasing is efficiently detected in all cases. These steps, in our opinion, are a necessary precondition for rigorous static analysis. regards Peter Alexandre E. Kopilovitch wrote: > Wojtek Narczynski wrote: > > >>This worry is unclear to me: >> >> >>>>And only one seems still valid: it is about complex >>>>expressions where a function call may be used as >>>>an actual argument for another function. >> >>I don't see how adding IN OUT arguments could make things worse in >>this matter. > > > Look at this formulae: > > F(A) + G(A); > > [snip]