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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9a7e0c43216f4def X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: "out" or "access" Date: 1998/10/21 Message-ID: #1/1 X-Deja-AN: 403552898 Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.camb.inmet.com References: <908956499.754394@dedale.pandemonium.fr> Organization: Intermetrics, Inc. Newsgroups: comp.lang.ada Date: 1998-10-21T00:00:00+00:00 List-Id: =:-) Vincent (vb@bruker.fr) wrote: : What's the best way ? An "out" parameter is always preferable to an "access" parameter, in my view. Use an "access" parameter only if you need an access value when inside the called subprogram for some reason. This usually only happens when interfacing to some other language, or some preexisting subsystem of some sort. : package B is : ... : The_Procedure ( The_Parameter: out Integer ); : -- or The_Procedure ( The_Parameter: access Integer ); : ... : end B; : ... : package body A is : ... : g_Toto: Integer; -- or aliased Integer : ... : procedure The_Other_Procedure is : begin : ... : B.The_Procedure ( g_Toto ); : -- or B.The_Procedure( g_Toto'Access ); : ... : end; : ... : end A; : Thanks. -- -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Burlington, MA USA An AverStar Company