Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!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: <2002@uwbull.uwbln.UUCP> Date: 29 Nov 89 12:21:45 GMT References: <547.nlhp3@oracle.nl> <1989Nov16.012439.6405@virtech.uucp> <497@mwtech.UUCP> Distribution: comp Organization: UniWare GmbH, Berlin Lines: 21 In article <497@mwtech.UUCP>, martin@mwtech.UUCP (Martin Weitzel) writes: > My personal opinion is, that the SVID just did forget to mention. > [...] I agree totally although i wonder why they purged the sentence in question which was present in the old manual pages. The problem is, that some implementors will read the specs and implement what is written there. You as a software developer will have a hard time argueing ``well, but look, your implementation doesnt make sense'' when your program dumps core and the words are against you :-( > Last and final: From the very beginning SVID stated, they will strongly > consider full conformance to X3J11 - and X3J11 has no doubt about that > argv[argc] is a null pointer. You should send a gripe to at&t :-) I dont have my XPG3 at hand, but i bet its the same wording there! christoph -- # include Christoph Kuenkel/UniWare GmbH Kantstr. 152, 1000 Berlin 12, West Germany ck@tub.BITNET ckl@uwbln {unido,tmpmbx,tub}!uwbln!ckl