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,733faa8b7b00c147 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!proxad.net!fr.ip.ndsoftware.net!newsfeed.freenet.de!news-lei1.dfn.de!news.uni-jena.de!not-for-mail From: Adrian Knoth Newsgroups: comp.lang.ada Subject: Re: basic ada question Date: Fri, 19 Aug 2005 21:13:44 +0000 (UTC) Organization: loris.TV Message-ID: References: NNTP-Posting-Host: ppc201.mipool.uni-jena.de X-Trace: lc03.rz.uni-jena.de 1124486024 26642 141.35.13.101 (19 Aug 2005 21:13:44 GMT) X-Complaints-To: abuse@uni-jena.de NNTP-Posting-Date: Fri, 19 Aug 2005 21:13:44 +0000 (UTC) User-Agent: slrn/0.9.8.1 (Debian) Xref: g2news1.google.com comp.lang.ada:4203 Date: 2005-08-19T21:13:44+00:00 List-Id: Simon Wright wrote: >>> It seems to be optional and not required. >> You're not forced to use named parameters. It's just a feature to >> ease your life ;) > > System.Pool_Size.Deallocate > (Pool => System.Pool_Size.Stack_Bounded_Pool (Pool), > Address => Address, > Storage_Size => Storage_Size, > Alignment => Alignment); > > might look like overkill, but you can be sure it's what was meant. Though I agree in general, I often feel confused when the formal parameter is named like the right hand side. Especially when used in VHDL it's a drawback to have IO-ports and signals share the same name (you don't know whether you're connecting to a signal (multiple endpoints) or a port (single endpoints)) Of course the workaround is simple: special naming convention ;) JFTR -- mail: adi@thur.de http://adi.thur.de PGP: v2-key via keyserver Sollte es Dir gut gehen, mach Dir nichts draus. Das geht vorbei.