summaryrefslogtreecommitdiff
path: root/manual/=process.texinfo
diff options
context:
space:
mode:
Diffstat (limited to 'manual/=process.texinfo')
-rw-r--r--manual/=process.texinfo46
1 files changed, 23 insertions, 23 deletions
diff --git a/manual/=process.texinfo b/manual/=process.texinfo
index 63c723ed37..4618cff5fa 100644
--- a/manual/=process.texinfo
+++ b/manual/=process.texinfo
@@ -90,7 +90,7 @@ Option names are single alphanumeric (as for @code{isalnum};
see @ref{Classification of Characters}).
@item
-Certain options require an argument. For example, the @samp{-o}
+Certain options require an argument. For example, the @samp{-o}
command of the ld command requires an argument---an output file name.
@item
@@ -326,7 +326,7 @@ The value of an environment variable can be accessed with the
@pindex stdlib.h
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypefun {char *} getenv (const char *@var{name})
This function returns a string that is the value of the environment
variable @var{name}. You must not modify this string. In some systems
@@ -353,7 +353,7 @@ may not be available in other systems.
You can deal directly with the underlying representation of environment
objects to add more variables to the environment (for example, to
communicate with another program you are about to execute; see
-@ref{Executing a File}).
+@ref{Executing a File}).
@comment unistd.h
@comment POSIX.1
@@ -410,7 +410,7 @@ uses this environment variable, as do many shells and other utilities
which are implemented in terms of those functions.
The syntax of a path is a sequence of directory names separated by
-colons. An empty string instead of a directory name stands for the
+colons. An empty string instead of a directory name stands for the
current directory. (@xref{Working Directory}.)
A typical value for this environment variable might be a string like:
@@ -499,10 +499,10 @@ more detail in @ref{Signal Handling}. The @code{abort} function causes
a terminal that kills the program.
@menu
-* Normal Program Termination::
+* Normal Program Termination::
* Exit Status:: Exit Status
* Cleanups on Exit:: Cleanups on Exit
-* Aborting a Program::
+* Aborting a Program::
* Termination Internals:: Termination Internals
@end menu
@@ -510,7 +510,7 @@ a terminal that kills the program.
@subsection Normal Program Termination
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypefun void exit (int @var{status})
The @code{exit} function causes normal program termination with status
@var{status}. This function does not return.
@@ -521,7 +521,7 @@ function or by calling @code{exit}, the following actions occur in
sequence:
@enumerate
-@item
+@item
Functions that were registered with the @code{atexit} or @code{on_exit}
functions are called in the reverse order of their registration. This
mechanism allows your application to specify its own ``cleanup'' actions
@@ -529,12 +529,12 @@ to be performed at program termination. Typically, this is used to do
things like saving program state information in a file, or unlock locks
in shared data bases.
-@item
+@item
All open streams are closed; writing out any buffered output data. See
@ref{Opening and Closing Streams}. In addition, temporary files opened
with the @code{tmpfile} function are removed; see @ref{Temporary Files}.
-@item
+@item
@code{_exit} is called. @xref{Termination Internals}
@end enumerate
@@ -582,7 +582,7 @@ are declared in the file @file{stdlib.h}.
@pindex stdlib.h
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypevr Macro int EXIT_SUCCESS
This macro can be used with the @code{exit} function to indicate
successful program completion.
@@ -593,7 +593,7 @@ expression.
@end deftypevr
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypevr Macro int EXIT_FAILURE
This macro can be used with the @code{exit} function to indicate
unsuccessful program completion in a general sense.
@@ -611,14 +611,14 @@ mean that there was difficulty in opening the files.
@subsection Cleanups on Exit
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypefun int atexit (void (*@var{function}))
The @code{atexit} function registers the function @var{function} to be
called at normal program termination. The @var{function} is called with
no arguments.
The return value from @code{atexit} is zero on success and nonzero if
-the function cannot be registered.
+the function cannot be registered.
@end deftypefun
@comment stdlib.h
@@ -666,7 +666,7 @@ for this function is in @file{stdlib.h}.
@pindex stdlib.h
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypefun void abort ()
The @code{abort} function causes abnormal program termination, without
executing functions registered with @code{atexit} or @code{on_exit}.
@@ -751,7 +751,7 @@ primitive functions to do each step individually instead.
program.
* Process Completion:: How to tell when a child process has
completed.
-* Process Completion Status:: How to interpret the status value
+* Process Completion Status:: How to interpret the status value
returned from a child process.
* BSD wait Functions:: More functions, for backward
compatibility.
@@ -771,7 +771,7 @@ until the subprogram terminates before you can do anything else.
@pindex stdlib.h
@comment stdlib.h
-@comment ANSI
+@comment ISO
@deftypefun int system (const char *@var{command})
This function executes @var{command} as a shell command. In the GNU C
library, it always uses the default shell @code{sh} to run the command.
@@ -937,7 +937,7 @@ The child doesn't inherit alarms set by the parent process.
The set of pending signals (@pxref{Delivery of Signal}) for the child
process is cleared. (The child process inherits its mask of blocked
signals and signal actions from the parent process.)
-@end itemize
+@end itemize
@comment unistd.h
@@ -1009,7 +1009,7 @@ passed as the last such argument.
@deftypefun int execve (const char *@var{filename}, char *const @var{argv}@t{[]}, char *const @var{env}@t{[]})
This is similar to @code{execv}, but permits you to specify the environment
for the new program explicitly as the @var{env} argument. This should
-be an array of strings in the same format as for the @code{environ}
+be an array of strings in the same format as for the @code{environ}
variable; see @ref{Environment Access}.
@end deftypefun
@@ -1369,7 +1369,7 @@ equivalent macros.
If @var{usage} is a null pointer, this function is equivalent to
@code{waitpid (-1, @var{status_ptr}, @var{options})}.
-The @var{usage} argument may also be a pointer to a
+The @var{usage} argument may also be a pointer to a
@code{struct rusage} object. Information about system resources used by
terminated processes (but not stopped processes) is returned in this
structure.
@@ -1384,7 +1384,7 @@ hasn't been written yet. Put in a cross-reference here.
If @var{usage} is a null pointer, this function is equivalent to
@code{waitpid (@var{pid}, @var{status_ptr}, @var{options})}.
-The @var{usage} argument may also be a pointer to a
+The @var{usage} argument may also be a pointer to a
@code{struct rusage} object. Information about system resources used by
terminated processes (but not stopped processes) is returned in this
structure.
@@ -1410,7 +1410,7 @@ argument using the equivalent of @samp{sh -c @var{command}}.
/* @r{Execute the command using this shell program.} */
#define SHELL "/bin/sh"
-int
+int
my_system (char *command)
@{
int status;
@@ -1442,7 +1442,7 @@ example.
Remember that the first @code{argv} argument supplied to the program
represents the name of the program being executed. That is why, in the
call to @code{execl}, @code{SHELL} is supplied once to name the program
-to execute and a second time to supply a value for @code{argv[0]}.
+to execute and a second time to supply a value for @code{argv[0]}.
The @code{execl} call in the child process doesn't return if it is
successful. If it fails, you must do something to make the child