Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!decwrl!pyramid!ut-sally!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.lang.c
Subject: Re: Passing arguments to C programs
Message-ID: <265@hadron.UUCP>
Date: Tue, 18-Feb-86 01:34:37 EST
Article-I.D.: hadron.265
Posted: Tue Feb 18 01:34:37 1986
Date-Received: Wed, 19-Feb-86 07:31:14 EST
References: <842@megaron.UUCP> <1820@brl-tgr.ARPA>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 20
Summary: ... and even stand-alone.

In article <983@brl-smoke.ARPA> gwyn@brl.ARPA writes:
>The requirements for a hosted C environment are given in section
>B.1.2.2 of the X3J11 draft standard.  ...
>     ... there is a strong implication that the environment must
>be able to supply [args] to a C program at start-up.  This would
>not be required of a freestanding environment C implementation,
>of course.

I don't see why "of course."  Using the System V stand-alone shell,
I've gotten unix to happily accept command-line arguments specifying
root, initial swap, dump, and pipe devices and other parameters.
Perhaps "of course" applies just to the idea that it's not required
of less fortunate systems?

Note that accepting arguments is possible to most stand-alone programs
on System V even without the stand-alone shell.  They just prompt for
their args and read them in from the keyboard.
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}