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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9d303864ae4c70ad,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-04-07 13:34:36 PST Path: archiver1.google.com!news1.google.com!news.glorb.com!news.cs.univ-paris8.fr!proxad.net!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Reprise: 'in out' parameters for functions Date: 07 Apr 2004 16:31:44 -0400 Organization: Cuivre, Argent, Or Message-ID: NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1081369918 45080 212.85.156.195 (7 Apr 2004 20:31:58 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Wed, 7 Apr 2004 20:31:58 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:6821 Date: 2004-04-07T16:31:44-04:00 I just ran across a need for an 'in out' parameter in a function, in "real code", so I thought I post it here "just for fun" :). This is what I wanted to declare: function Parse (Error_Label : in String; Token : in out Token_List.List_Iterator) return String; -- Process Token, which should contain '([Config_File =>] )'. -- Return the string. -- Delete parsed tokens from Token. Token must be 'in out', because the next parse function called wants to work on the stuff after the config file. Parse must be a function, because I'm returning a String. The work-around is to use a procedure and a bounded string: procedure Parse (Error_Label : in String; Token : in out Token_List.List_Iterator; Config_File_Name : out OpenToken.Buffers.Bounded_String); In this instance, the body of Parse deals with OpenToken.Buffers.Bounded_String anyway, so there's no actual new overhead introduced. But the user interface is not as clean as it could be. -- -- Stephe