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: Fri, 09 Jul 2004 22:50:32 +0100 Message-ID: References: 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 Ao33kg26VvqN4nmvtG+JDwulVxNZyFCDRRCWuY/Cf438oQgsQ= User-Agent: Opera M2/7.51 (Win32, build 3798) Xref: g2news1.google.com comp.lang.ada:2135 Date: 2004-07-09T22:50:32+01:00 List-Id: On Fri, 09 Jul 2004 21:29:08 GMT, Keith Thompson wrote: > ... > It seems counterintuitive to associate the parameter > passing method with a subtype rather than with a formal > parameter. > > What about something like this? > > function Wibble (N: in Integer); > for Wibble'Parameter_Passing use ( N => EAX ); > > Adjust names and syntax to taste. I agree, and I've outlined a scheme in another post in this thread. -- Nick Roberts