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,92d1af21ade61406
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-11-06 09:29:49 PST
Path: 
 archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: Problems with 'class, help anyone?
Date: 06 Nov 2002 12:22:39 -0500
Organization: NASA Goddard Space Flight Center (skates.gsfc.nasa.gov)
Message-ID: <u7kfqlijk.fsf@gsfc.nasa.gov>
References: <pan.2002.10.29.04.48.24.252092@student.liu.se>
 <3DBE2593.9080800@worldnet.att.net>
 <pan.2002.10.30.05.27.31.99377@student.liu.se>
 <3DBF9437.8090408@worldnet.att.net>
 <pan.2002.11.05.02.40.38.47887@student.liu.se>
 <3DC74F23.80308@worldnet.att.net> <u7kfs9bex.fsf@gsfc.nasa.gov>
 <wcc8z07fy6d.fsf@shell01.TheWorld.com> <upttjnkmb.fsf@wanadoo.fr>
 <4519e058.0211060719.210d21bd@posting.google.com>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 1036604019 17257 128.183.235.92 (6 Nov 2002
 17:33:39 GMT)
X-Complaints-To: usenet@news.gsfc.nasa.gov
NNTP-Posting-Date: 6 Nov 2002 17:33:39 GMT
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Xref: archiver1.google.com comp.lang.ada:30472
Date: 2002-11-06T17:33:39+00:00
List-Id: <comp.lang.ada>

dennison@telepath.com (Ted Dennison) writes:

> Pascal Obry <p.obry@wanadoo.fr> wrote in message
> news:<upttjnkmb.fsf@wanadoo.fr>... > Well, as Stephen, I think "in"
> should always be there. This is also part of my > style guide. With
> a nice formatting it reads very well:
> > 
> >    procedure Call
> >      (P1 : in     Integer;
> >       P2 : in out Integer;
> >       P4 :    out Integer;
> >       P3 : access Integer);
> 
> I used to feel that way too. However, a couple of years ago Robert
> Dewar mananged to convince me that it should not not be put in
> functions, as its essentially a redundancy there ("out" isn't
> allowed). So now my personal style guide reads the same as yours, with
> an exception for functions, which should not have any modes on their
> parameters (unless "access" is used).

I'd almost go along with that; it's a good reason to leave it out.
However, the One True Editor* relies on the presence of "in" to
correctly colorize the following type name. I'm really used to seeing
types in green, so I'm leaving in the "in". At least until the editor
is "fixed".

-- 
-- Stephe

*Emacs, of course :).