about summary refs log tree commit diff
diff options
context:
space:
mode:
-rw-r--r--ChangeLog4
-rw-r--r--manual/examples/longopt.c2
-rw-r--r--manual/pipe.texi12
3 files changed, 12 insertions, 6 deletions
diff --git a/ChangeLog b/ChangeLog
index 8ac5c69956..d053faf7d2 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+Wed May 15 18:59:38 1996  Roland McGrath  <roland@delasyd.gnu.ai.mit.edu>
+
+	* manual/examples/longopt.c: Include stdlib.h and getopt.h.
+
 Tue May 14 03:36:21 1996  Ulrich Drepper  <drepper@cygnus.com>
 
 	* sysdeps/unix/sysv/linux/Makefile [$subdir == misc] (headers):
diff --git a/manual/examples/longopt.c b/manual/examples/longopt.c
index d5c841f24a..9d6bd53c0f 100644
--- a/manual/examples/longopt.c
+++ b/manual/examples/longopt.c
@@ -1,4 +1,6 @@
 #include <stdio.h>
+#include <stdlib.h>
+#include <getopt.h>
 
 /* Flag set by @samp{--verbose}.  */
 static int verbose_flag;
diff --git a/manual/pipe.texi b/manual/pipe.texi
index 773dc4aac8..274b93d427 100644
--- a/manual/pipe.texi
+++ b/manual/pipe.texi
@@ -113,7 +113,7 @@ function; see @ref{Running a Command}.  It executes the shell command
 command to complete, it creates a pipe to the subprocess and returns a
 stream that corresponds to that pipe.
 
-If you specify a @var{mode} argument of @code{"r"}, you can read from the 
+If you specify a @var{mode} argument of @code{"r"}, you can read from the
 stream to retrieve data from the standard output channel of the subprocess.
 The subprocess inherits its standard input channel from the parent process.
 
@@ -193,11 +193,11 @@ system.
 @section Atomicity of Pipe I/O
 
 Reading or writing pipe data is @dfn{atomic} if the size of data written
-is less than @code{PIPE_BUF}.  This means that the data transfer seems
-to be an instantaneous unit, in that nothing else in the system can
-observe a state in which it is partially complete.  Atomic I/O may not
-begin right away (it may need to wait for buffer space or for data), but
-once it does begin, it finishes immediately.
+is not greater than @code{PIPE_BUF}.  This means that the data transfer
+seems to be an instantaneous unit, in that nothing else in the system
+can observe a state in which it is partially complete.  Atomic I/O may
+not begin right away (it may need to wait for buffer space or for data),
+but once it does begin, it finishes immediately.
 
 Reading or writing a larger amount of data may not be atomic; for
 example, output data from other processes sharing the descriptor may be