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-27 09:07:16 PST Path: archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!zeus.visi.com!news-out.visi.com!green.octanews.net!news-out.octanews.net!news.glorb.com!newsfeed.mountaincable.net!nx02.iad01.newshosting.com!newshosting.com!diablo.voicenet.com!nntp.abs.net!ash.uu.net!spool.news.uu.net!not-for-mail Date: Fri, 27 Feb 2004 12:06:40 -0500 From: Hyman Rosen User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: left-to-right (was In-Out Parameters for functions) References: <4020C947.81A6D703@0.0> <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> <3c0u3054mganvifajj3g6jealh07qoi1h7@4ax.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1077901609.542940@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: 1077901609 1217 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:5904 Date: 2004-02-27T12:06:40-05:00 List-Id: Stephen Leake wrote: > Ok. That is a good example. > > So, Hymen; we now have (at least) two good examples of optimizations > that are useful, but would not be possible if the language required > right-to-left parameter evaluation. > > Do you agree the cost of changing is to right-to-left is not worth the > gain? That's "Hyman". I don't think the array index case is a good counterexample; compilers are now very good at dealing with loop induction variables, and I doubt that generated code for this would be affected by l-to-r. RB's case was better. Whether such cases are sufficient is a matter of judgement, but the existence of a good optimization example means that l-to-r will never be adopted (not that there was a chance anyway).