Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!dawn!stpeters
From: stpeters@dawn.steinmetz (Dick St.Peters)
Newsgroups: comp.unix.wizards
Subject: Re: have I found a bug in K&R?
Message-ID: <7639@steinmetz.steinmetz.UUCP>
Date: Thu, 15-Oct-87 16:41:24 EDT
Article-I.D.: steinmet.7639
Posted: Thu Oct 15 16:41:24 1987
Date-Received: Sat, 17-Oct-87 09:10:38 EDT
References: <517@hubcap.UUCP> <321@laticorp.UUCP> <7608@steinmetz.steinmetz.UUCP> <324@laticorp.UUCP>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: stpeters@dawn.UUCP (Dick St.Peters)
Organization: General Electric CRD, Schenectady, NY
Lines: 22
Keywords: argv definition

In article <324@laticorp.UUCP> sarah@laticorp.UUCP (Sarah Groves Hobart) writes:
>Right.  An array name IS a constant, so something like:
>
>   ptr = &array_name;
>
>is illegal.  I was referring to their equivalence as formal parameters
>in a function definition.

Ok, but isn't the non-difference in this case obvious to anyone who
knows what a "formal parameter" is?

As someone who has spent many hours trying to introduce to C people
who are basically non-programmers but must do a little programming, is
there any way I can get you folks to stop using the term "formal
parameter" when "function argument" or "procedure argument" will do as
well?  I am tired of translating and being asked what an informal
parameter is.
--
Dick St.Peters                        
GE Corporate R&D, Schenectady, NY
stpeters@ge-crd.arpa              
uunet!steinmetz!stpeters