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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ac02560f0af03a21 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-02 05:29:28 PST Path: archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!crtntx1-snh1.gtei.net!news.gtei.net!newsfeed1.easynews.com!easynews.com!easynews!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!0f19ed38!not-for-mail From: "Frank J. Lhota" Newsgroups: comp.lang.ada References: <3fec7c21$0$4764$61fed72c@news.rcn.com> <4iBIb.8173$qS3.498@nwrdny03.gnilink.net> <1072883131.278899@master.nyc.kbcfp.com> <1072891494.595791@master.nyc.kbcfp.com> <1072899508.453543@master.nyc.kbcfp.com> <1072906542.723974@master.nyc.kbcfp.com> <3ff38b16$0$4759$61fed72c@news.rcn.com> <3ff44baf$0$4754$61fed72c@news.rcn.com> <3ff4ba22$0$4761$61fed72c@news.rcn.com> Subject: Re: GNAT parameter passing, C-style? X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Date: Fri, 02 Jan 2004 13:29:27 GMT NNTP-Posting-Host: 151.203.242.46 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1073050167 151.203.242.46 (Fri, 02 Jan 2004 08:29:27 EST) NNTP-Posting-Date: Fri, 02 Jan 2004 08:29:27 EST Xref: archiver1.google.com comp.lang.ada:4039 Date: 2004-01-02T13:29:27+00:00 List-Id: "Hyman Rosen" wrote in message news:G96Jb.30096$tY5.28719@nwrdny01.gnilink.net... > Frank J. Lhota wrote: > > Yes, but what about the callee? > > What *about* the calee? It sees the arguments the same > way, with the first at the top of the stack and the others > lower down. Come on, work it out for yourself. There's no > difference between pushing from right to left, or reserving > space then filling from left to right. The resulting picture > in memory is the same. OK, I get the picture. We're beyond the discussion of the convention, and are now discussing how the implementation is implemented. Basically what you're saying is that one can "process" arguments from left to right and get the same effect as pushing the argurments from right to left. On that point, I totally agree.