Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!drutx!houxe!hogpc!houti!ariel!vax135!floyd!cmcl2!seismo!hao!hplabs!hp-pcd!hp-dcd!donn
From: donn@hp-dcd.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Orphaned Response
Message-ID: <3200006@hp-dcd.UUCP>
Date: Fri, 15-Jun-84 19:22:00 EDT
Article-I.D.: hp-dcd.3200006
Posted: Fri Jun 15 19:22:00 1984
Date-Received: Fri, 15-Jun-84 01:09:46 EDT
References: <-194800@rlgvax.UUCP>
Organization: Hewlett-Packard Fort Collins Systems Division - Fort Collins, CO
Lines: 24
Nf-ID: #R:rlgvax:-194800:hp-dcd:3200006:37777777600:952




Nf-From: hp-dcd!donn    Jun 12 15:22:00 1984


I suggest that it is wise to take AT&T's documentation, or the fact that
something is not documented, with a grain of salt;  there is probably no
clear rule to follow as to whether the error is in the code, documentation
or the feature is "not ready yet".  I've found a lot of errors in both
undocumented features and documented non-features.  Granted, if it's not
documented, one should be more skeptical.

The following example is the kind of thing that makes me nervous about
trusting the documentation without confirming the details.

A comparison of the semop(2) manual pages for System V Release 1 (a.k.a.
5.0) and Release 2:

	V.1:  Semop is used to atomically perform an array of semaphore
	      operations...

	V.2:  Semop is uset to automatically perform an array of semaphore
	      operations...

I sincerely hope that the Release 1 version is correct, and some how the
change crept into the manual on its own.

Donn Terry
Hewlett-Packard