Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: have I found a bug in K&R?
Message-ID: <9015@mimsy.UUCP>
Date: Fri, 16-Oct-87 10:25:08 EDT
Article-I.D.: mimsy.9015
Posted: Fri Oct 16 10:25:08 1987
Date-Received: Sun, 18-Oct-87 00:19:45 EDT
References: <517@hubcap.UUCP> <321@laticorp.UUCP> <7608@steinmetz.steinmetz.UUCP> <7639@steinmetz.steinmetz.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 18
Keywords: argv definition

In article <7639@steinmetz.steinmetz.UUCP> stpeters@dawn.steinmetz
(Dick St.Peters) writes:
>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?

It is rare that `function argument' will do as well as `formal
parameter'.  `Function argument' can also mean `actual parameter',
and formal-parameter pointer/array conversions are not performed
on actual parameters.

(Jargon *does* have its uses, and every occupation has its jargon.
Perhaps the first thing you should introduce is the jargon.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris