Xref: utzoo comp.lang.c:26558 comp.software-eng:3051
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!rosarita!raymond
From: raymond@rosarita.berkeley.edu (Raymond Chen)
Newsgroups: comp.lang.c,comp.software-eng
Subject: Re: Currency Quotes
Message-ID: <1990Mar4.213359.14687@agate.berkeley.edu>
Date: 4 Mar 90 21:33:59 GMT
References: <803@xyzzy.UUCP> <8229@hubcap.clemson.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: raymond@rosarita.UUCP (Raymond Chen)
Organization: U.C. Berkeley
Lines: 24

In article <8229@hubcap.clemson.edu> billwolf@hazel.cs.clemson.edu writes:
>   a) inappropriate, since the static nature of the rates is part
>   of the specification and should not be listed in the defects
>   section, 

Okay, part of the problem is not realizing that the BUGS section
of a man page is misnamed.

	The BUGS section is also somewhat misnamed.  Defects reported
	here aren't so much bugs as shortcomings---simple bugs should
	be fixed before the command in installed.

				-Kernighan and Pike
				 "The UNIX Programming Environment"
				 p. 311

It really should be called "POTENTIALLY PROBLEM-CAUSING BEHAVIOR".  So
defects in the specification or any behavior which someone might
possibly think is a bug (even if it isn't) go into the BUGS section.
For example, the sentence

	The precedence rules are somewhat nonintuitive.

belongs in the BUGS section even though it isn't a bug.