Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.unix.wizards
Subject: Re: null pointer problems and AT&T (was: att & osf)
Message-ID: <1269@unisoft.UUCP>
Date: 31 Aug 88 21:10:13 GMT
References: <4964@killer.DALLAS.TX.US> <3395@vpk4.UUCP> <1988Aug19.204836.23395@utzoo.uucp> <3165@homxc.UUCP> <1988Aug26.194505.25724@utzoo.uucp> <8391@smoke.ARPA>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Lines: 18

In article <8391@smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <1988Aug26.194505.25724@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>>a little bird tells me that *THE SVVS ITSELF* has NULL-pointer problems!!!
>
>???  What could this possibly mean?  I don't recall seeing any SOURCE CODE
>in the SVID!  And how could an INTERFACE SPEC have a "null pointer problem"?

Who was talking about SVID ?  The SVVS is not the same thing as the SVID.
SVVS is the System V Verification Suite.  It has to test things within the SVID
to make sure that they work properly, i.e. it tests an INTERFACE SPEC.  The
Test Suite itself is a PROGRAM, and it probably has NULL POINTER PROBLEMS.

[I've had to count to ten after reading your posts more than once.]
--
 "
Roan Anderson, Software Engineer, Configuration Management
UniSoft Corporation, Emeryville, CA.
*** The above opinions are my own and not those of my employer. ***