Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!uunet!mcsun!unido!tub!uwbln!ckl
From: ckl@uwbln.UUCP (Christoph Kuenkel)
Newsgroups: comp.unix.wizards
Subject: Re: Why isn't argv[argc]==(char *)0 ?
Keywords: X/OS, Olivetti, LSX, coredump
Message-ID: <1989@uwbull.uwbln.UUCP>
Date: 23 Nov 89 13:08:12 GMT
References: <547.nlhp3@oracle.nl> <1989Nov16.012439.6405@virtech.uucp> <1635@ctisbv.cti-software.nl>
Distribution: comp
Organization: UniWare GmbH, Berlin
Lines: 18

In article <1635@ctisbv.cti-software.nl>, pim@cti-software.nl (Pim Zandbergen) writes:
> guy@auspex.auspex.com (Guy Harris) writes:
> >(I.e., unless you have to deal with an archaic UNIX or a Mutant UNIX
> >From Hell, you can count on argv[argc] == 0.)
> 
> In X/OS, a SYSV/BSD hybrid operating system for the Olivetti LSX
> minicomputers, a reference to argv[argc] will make your program dump core.
which is SVID conformant.  as mentioned before, the SVID does not say 
anything about argv[argc] but states that

	"argc is the argument count, argv is an array of character pointers
	 to the argument themselves"

thus *(argv[argc]) may legally dump core.
-- 
# include <std/disclaimer.h>
Christoph Kuenkel/UniWare GmbH       Kantstr. 152, 1000 Berlin 12, West Germany
ck@tub.BITNET                ckl@uwbln             {unido,tmpmbx,tub}!uwbln!ckl