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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable 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 00:19:39 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: In-Out Parameters for functions Date: 27 Jan 2004 03:18:08 -0500 Organization: Cuivre, Argent, Or Message-ID: References: <1075159458.149886@master.nyc.kbcfp.com> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1075191509 28508 80.67.180.195 (27 Jan 2004 08:18:29 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Tue, 27 Jan 2004 08:18:29 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.3 Precedence: list List-Id: Gateway to the comp.lang.ada Usenet newsgroup List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:4884 Date: 2004-01-27T03:18:08-05:00 Hyman Rosen writes: > Robert A Duff wrote: > > It does seem of some value to attempt to make sure "order doesn't matter". > > But since this will never be the case in Ada, the next best thing is to > define the order. Hmm. It's very unlikely that Ada will change to define the order of execution in expressions. There are good reasons to leave it undefined (different optimizations for different targets or speed/space goals, for example), and changing it would be work for existing compilers. On the other hand, I can enforce a style rule that says "don't write expressions whose result depends on order of execution". I could even write an ASIS tool to help enforce that. I think this style rule is what Robert is suggesting here. So I'm not clear what you are saying, Hymen. -- -- Stephe