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-Thread: 103376,46a68619f4362304 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail From: "Nick Roberts" Newsgroups: comp.lang.ada Subject: Re: Specifying parameter passing convention and place (register) Date: Thu, 08 Jul 2004 19:10:46 +0100 Message-ID: References: <$RVvBAOy5BPi@eisner.encompasserve.org> <6qg+KjvqRKch@eisner.encompasserve.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: news.uni-berlin.de uk4V35MrW4XkUoXmj5w6Bgw0as+LYPLJhhBOm+CFhFLFMFNRM= User-Agent: Opera M2/7.51 (Win32, build 3798) Xref: g2news1.google.com comp.lang.ada:2126 Date: 2004-07-08T19:10:46+01:00 List-Id: On Thu, 8 Jul 2004 10:09:06 -0400, Bob Spooner wrote: > Nick, > > If you look at the parameter passing mechanisms available when using > interface pragmas such as Export_Procedure, you may be able to specify > what > you want. Thanks Bob, but the options there don't seem to allow specification of the 'place' (register or location in the stack frame) to pass a parameter (or return result). I outlined a couple of pragmas I might use in a sibling message in this thread. -- Nick Roberts