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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,6a0391eb7e0327d5
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-11 09:18:36 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: gautier_niouzes@hotmail.com (Gautier)
Newsgroups: comp.lang.ada
Subject: Re: Ada style of passing 'in' parameters considered dangerous?
Date: 11 Feb 2003 09:18:36 -0800
Organization: http://groups.google.com/
Message-ID: <17cd177c.0302110918.71881340@posting.google.com>
References: <86isvuzabx.fsf@hoastest1-8c.hoasnet.inet.fi>
 <17cd177c.0302110114.2c46b52@posting.google.com>
NNTP-Posting-Host: 213.173.163.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1044983916 5265 127.0.0.1 (11 Feb 2003 17:18:36
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 11 Feb 2003 17:18:36 GMT
Xref: archiver1.google.com comp.lang.ada:33997
Date: 2003-02-11T17:18:36+00:00
List-Id: <comp.lang.ada>

gautier_niouzes@hotmail.com (Gautier):

> See my other reply. IIRC, the worst were cases where procedure P
> calls Q, Q calls R and R modifies an IN parameter because it references
> also a [IN] OUT, then even the IN parameter of P is also modified after
> the call to Q. Add loops and so on... :-}

Sorry, I recalled wrong: the IN parameter cannot be passed as
a variable, since it is considered as a constant!
The security problem remains on one level (unless I'm missing
a combination, maybe with a pointed object where the pointer is IN ?)
________________________________________________________
Gautier  --  http://www.mysunrise.ch/users/gdm/gsoft.htm

NB: For a direct answer, e-mail address on the Web site!