Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: null pointer problems and AT&T (was: att & osf)
Message-ID: <8391@smoke.ARPA>
Date: 28 Aug 88 05:51:24 GMT
References: <4964@killer.DALLAS.TX.US> <3395@vpk4.UUCP> <1988Aug19.204836.23395@utzoo.uucp> <3165@homxc.UUCP> <1988Aug26.194505.25724@utzoo.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

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"?

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.  It was
not considered acceptable (I was told by a vendor doing a "validated port")
to simply quietly fix a bug; instead EVERY change to the source code had to
be thoroughly documented and justified.  The kind of people who are best at
idenitifying and fixing portability bugs are probably not eager to spend a
lot of effort on such trivial matters, so as a result they don't bother to
fix the problems UNLESS they have to (because their system is directly
affected).  That's another managerial problem..