Newsgroups: comp.unix.wizards
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: null pointer problems and AT&T (was: att & osf)
Message-ID: <1988Aug31.163933.28968@utzoo.uucp>
Organization: U of Toronto Zoology
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>
Date: Wed, 31 Aug 88 16:39:33 GMT

In article <8391@smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) 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"?

Uh, Doug, SVVS, not SVID.  The SVVS is a great pile of source code for
checking SVID compliance.  And I have it on good authority that it does
indeed have null-pointer problems.

>I think one of the reasons that bugs have persisted for a long time in UNIX
>System V products is that it is a major hassle getting one removed...

Yes, I've heard this as well, and I believe it.  "Source code control"
with a vengeance! :-)
-- 
Intel CPUs are not defective,  |     Henry Spencer at U of Toronto Zoology
they just act that way.        | uunet!attcan!utzoo!henry henry@zoo.toronto.edu