Re: Problems with 'class, help anyone?

[Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>]

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 :).