Path: utzoo!attcan!uunet!aplcen!samsung!gem.mps.ohio-state.edu!apple!fernwood!decwrl!chico.pa.dec.com!klee
From: klee@chico.pa.dec.com (Ken Lee)
Newsgroups: comp.unix.wizards
Subject: Re: Why isn't argv[argc]==(char *)0 ?
Message-ID: <2141@bacchus.dec.com>
Date: 20 Nov 89 23:43:11 GMT
References: <3053@cello.UUCP> <547.nlhp3@oracle.nl> <11606@smoke.BRL.MIL> <1979@uwbull.uwbln.UUCP>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Distribution: comp
Organization: DEC Western Software Laboratory
Lines: 11

In article <3053@cello.UUCP>, dcm@toysrus.uucp (dcm) writes:
> Argc should always be correct.  Who cares about argv[argc]?

The problem is that some UNIX functions, such as execv, do not take an
argc.  If your system does not force argv[argc]==NULL, you cannot
directly pass your argv (or the last part of it) to execv.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee