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-02-26 04:42:49 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: wojtek@power.com.pl (Wojtek Narczynski) Newsgroups: comp.lang.ada Subject: Re: In-Out Parameters for functions Date: 26 Feb 2004 04:42:49 -0800 Organization: http://groups.google.com Message-ID: <5ad0dd8a.0402260442.19e7383a@posting.google.com> References: <1075390647.405841@master.nyc.kbcfp.com> <1075907239.138068@master.nyc.kbcfp.com> <402232E9.3EE15B4B@0.0> <1075987360.225622@master.nyc.kbcfp.com> <40236C0B.E988E003@0.0> <1077634311.254581@master.nyc.kbcfp.com> <82347202.0402251405.2db2f3c5@posting.google.com> <1077747598.55635@master.nyc.kbcfp.com> NNTP-Posting-Host: 62.111.211.178 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1077799369 28470 127.0.0.1 (26 Feb 2004 12:42:49 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 26 Feb 2004 12:42:49 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:5836 Date: 2004-02-26T04:42:49-08:00 List-Id: Hello, > I would go with the order of the actual parameters, > not the order of the formal parameters. One goal of > specifying evaluation order is to have unsurprising > behavior, so saying > Battery(Catcher => GetName, Pitcher => GetName); > should assign the first name read to Catcher and the > second to Pitcher, regardless of the order of the formal > parameters of Battery. How about: Battery(Catcher => GetName then Pitcher => GetName, Doorman => GetName ); This way the change would not affect current code, and you could specify partial order. Regards, Wojtek