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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f28dd1d63a9466b2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-16 21:44:18 PST Path: bga.com!news.sprintlink.net!cs.utexas.edu!uunet!news.tele.fi!news.csc.fi!news.helsinki.fi!hydra.Helsinki.FI!holsti From: holsti@cs.Helsinki.FI (Niklas Holsti) Newsgroups: comp.lang.ada Subject: Re: Syntax question Date: 17 Mar 1995 05:44:18 GMT Organization: University of Helsinki, Department of Computer Science Distribution: world Message-ID: <3kb7ji$8ot@hydra.Helsinki.FI> References: <3jt25s$dim@felix.seas.gwu.edu><3k7t8o$4pt@hacgate2.hac.com> NNTP-Posting-Host: kypros.helsinki.fi Date: 1995-03-17T05:44:18+00:00 List-Id: In <3k7t8o$4pt@hacgate2.hac.com> dkusu@atc-1s.hac.com (David Kusuda) writes, among other things: >I agree with Michael's points regarding named parameter association. >But the named parameter association is also necessary to: > a) Specify the parameter list in an arbitrary order--I think this is a weak point > as far as readability/maintainability, but still a point. Named parameter association can also help maintenance. Recently, for peculiar and irrelevant reasons we changed the declaration of a subprogram from P (X: in Some_Type; Y: in Some_Type) to P (Y: in Some_Type; X: in Some_Type). Since our coding rules require named parameter association for all calls, we could do this without searching for and correcting all calls to P. The _meaning_ of X and Y was not changed, just their order in the parameter list. >Dave Niklas Holsti Working but not speaking for Space Systems Finland Ltd -- Niklas Holsti Space Systems Finland Ltd, phone +358 0 4354 3928 Tekniikantie 12, P.O. Box 324, FIN-02151 Espoo, Finland