Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!motcsd!hpda!hpcupt1!jamiller
From: jamiller@hpcupt1.HP.COM (Jim Miller)
Newsgroups: comp.lang.c
Subject: Re: C Community's Cavalier Attitude On Software Reliability
Message-ID: <5940018@hpcupt1.HP.COM>
Date: 10 Mar 90 00:02:06 GMT
References: <10529@alice.UUCP>
Organization: Hewlett Packard, Cupertino
Lines: 29

>> [Unix BUGS comments]
>> are honest indications of where problems may exist, and they do so
>> in language that can be enjoyed by the person reading the manual.  
>
>   Under no circumstances should a DEFECTS section contain flippant
>   comments such as "I tinker a lot, so things break, but then I fix
>   them, hooray", "Not bloody likely", or other comments which indicate
>   a cavalier attitude toward software reliability.  
>
>   DEFECTS sections exist for the purpose of listing known areas in
>   which an implementation does not correspond to the specification,
>   along with potential workarounds (if any) and the estimated date
>   of repair.  Now compare this with your typical Unix BUGS section.
>
>   Bill Wolfe, wtwolfe@hubcap.clemson.edu

.flame on
If you don't like the BUGS comments, don't read them, get some "real"
documentation instead.  This note is only 1/4 flippant.  Un*x documentation
looks like it is written by-for-and-to fun-(and work)-loving programmers.
If fun in your information bothers you, go elsewhere.  One reason I LIKE
the un*x community is because of the attitude you are attacking.  It is
written for programmers, not the rest of the world.  Other documentation is
being written for the rest.  People are making money informing the rest of
the world, especially  the various thought police who aggree with
the above "> " comments.
.flame off

   Jim - that's my ox you're goring - miller