AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-12-22 10:50:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Wed May 15 18:59:38 1996 Roland McGrath <roland@delasyd.gnu.ai.mit.edu>

Browse Source 
* manual/examples/longopt.c: Include stdlib.h and getopt.h.
This commit is contained in:
Roland McGrath 1996-05-15 23:05:44 +00:00
parent 0adc881c60
commit 46d9215f3b
3 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -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):

2
manual/examples/longopt.c
View File

@ -1,4 +1,6 @@
#include <stdio.h>
#include <stdlib.h>
#include <getopt.h>
/* Flag set by @samp{--verbose}. */
static int verbose_flag;

12
manual/pipe.texi
View File

@ -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