Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!minow
From: minow@decvax.UUCP (Martin Minow)
Newsgroups: net.lang.c
Subject: Passing arguments to C programs
Message-ID: <177@decvax.UUCP>
Date: Wed, 12-Feb-86 18:13:56 EST
Article-I.D.: decvax.177
Posted: Wed Feb 12 18:13:56 1986
Date-Received: Fri, 14-Feb-86 02:21:11 EST
References: <842@megaron.UUCP> <1820@brl-tgr.ARPA>
Reply-To: minow@decvax.UUCP (Martin minow)
Organization: DEC - ULTRIX Engineering Group
Lines: 26

In <814@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn) writes:

>In a hosted (as opposed to stand-alone) environment, yes, C requires
>that programs be able to obtain arguments specified at the time they
>are run.

There is nothing in the C language that requires command line argument
passing.  This is solely a feature of the Unix shell.  It can be
quite difficult to do on some operating systems which have different
assumptions about the way in which programs interact with their users.
(I speak from the experience of implementing command line argument
passing on at least 5 non-Unix operating systems.)

Other features of the shell (such as I/O redirection, filename wildcard
expansion, and the particular syntax of arguments) are equally not
a part of the language.

That developers have chosen to implement these features of the Unix
command language speaks more for the desire to be compatibile with
existing program usage -- it is not necessarily a good thing.

(Please note that these are my opinions only, and not necessarily
those of Digital.)

Martin Minow
decvax!minow