Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!genrad!panda!talcott!harvard!seismo!brl-adm!brl-smoke!smoke!woody%Juliet.Caltech.Edu@cit-hamlet.ARPA
From: woody%Juliet.Caltech.Edu@cit-hamlet.ARPA
Newsgroups: net.lang.c
Subject: Re: Command line arguments
Message-ID: <1463@brl-smoke.ARPA>
Date: Mon, 3-Mar-86 13:33:35 EST
Article-I.D.: brl-smok.1463
Posted: Mon Mar  3 13:33:35 1986
Date-Received: Wed, 5-Mar-86 05:45:35 EST
Sender: news@brl-smoke.ARPA
Lines: 22

>   [ Wayne Throop ]
>>  [ Carl Kuck ]

>>  2.  Command-line arguments are a part of C.
>>      Ref: K&R, chapter 5.11
>
>   Again, you don't catch on to subtleties.  The phrase is
>   "command-line arguments *or* parameters.  In fact, careful reading of
>   K&R convinces me that C may be correctly implemented on systems that
>   (shudder) *have* *no* *commands* *or* *command* *lines*, let alone
>   "command-line arguments."

    Like the Macintosh, where (despite Apple Computers) C seems to be the
de-facto programming language.  Under the Finder (read: Shell), running a 
program is done by double-clicking the icon representing the program with
the mouse, and arguments may be passed by shift-clicking the appropriate
file icons before double-clicking the program icon.  Command lines?  What
command lines?  Do you see any command lines?

         - William Woody
      NET  Woody%Romeo@Hamlet.Caltech.Edu
   USNAIL  1-54 Lloyd, Caltech / Pasadena, CA 91126