diff options
Diffstat (limited to 'manual')
| -rw-r--r-- | manual/arith.texi | 20 | ||||
| -rw-r--r-- | manual/conf.texi | 16 | ||||
| -rw-r--r-- | manual/creature.texi | 2 | ||||
| -rw-r--r-- | manual/filesys.texi | 30 | ||||
| -rw-r--r-- | manual/intro.texi | 2 | ||||
| -rw-r--r-- | manual/llio.texi | 8 | ||||
| -rw-r--r-- | manual/maint.texi | 51 | ||||
| -rw-r--r-- | manual/math.texi | 34 | ||||
| -rw-r--r-- | manual/message.texi | 70 | ||||
| -rw-r--r-- | manual/pattern.texi | 4 | ||||
| -rw-r--r-- | manual/search.texi | 18 | ||||
| -rw-r--r-- | manual/signal.texi | 2 | ||||
| -rw-r--r-- | manual/socket.texi | 2 | ||||
| -rw-r--r-- | manual/startup.texi | 2 | ||||
| -rw-r--r-- | manual/stdio.texi | 24 | ||||
| -rw-r--r-- | manual/string.texi | 26 | ||||
| -rw-r--r-- | manual/time.texi | 4 | ||||
| -rw-r--r-- | manual/users.texi | 2 |
18 files changed, 163 insertions, 154 deletions
diff --git a/manual/arith.texi b/manual/arith.texi index 2e418838db..431b4dbfec 100644 --- a/manual/arith.texi +++ b/manual/arith.texi @@ -12,7 +12,7 @@ These functions are declared in the header files @file{math.h} and * Not a Number:: Making NaNs and testing for NaNs. * Imaginary Unit:: Constructing complex Numbers. * Predicates on Floats:: Testing for infinity and for NaNs. -* Floating-Point Classes:: Classifiy floating-point numbers. +* Floating-Point Classes:: Classify floating-point numbers. * Operations on Complex:: Projections, Conjugates, and Decomposing. * Absolute Value:: Absolute value functions. * Normalization Functions:: Hacks for radix-2 representations. @@ -41,13 +41,13 @@ these situations. There is a special value for infinity. @comment math.h @comment ISO @deftypevr Macro float_t INFINITY -A expression representing the inifite value. @code{INFINITY} values are +A expression representing the infinite value. @code{INFINITY} values are produce by mathematical operations like @code{1.0 / 0.0}. It is possible to continue the computations with this value since the basic operations as well as the mathematical library functions are prepared to handle values like this. -Beside @code{INFINITY} also the value @code{-INIFITY} is representable +Beside @code{INFINITY} also the value @code{-INFINITY} is representable and it is handled differently if needed. It is possible to test a variables for infinite value using a simple comparison but the recommended way is to use the the @code{isinf} function. @@ -103,7 +103,7 @@ such as by defining @code{_GNU_SOURCE}, and then you must include @pindex complex.h To construct complex numbers it is necessary have a way to express the imaginary part of the numbers. In mathematics one uses the symbol ``i'' -to mark a number as imaginary. For convenienve the @file{complex.h} +to mark a number as imaginary. For convenience the @file{complex.h} header defines two macros which allow to use a similar easy notation. @deftypevr Macro float_t _Imaginary_I @@ -284,7 +284,7 @@ situation the function be absolutely necessary one can use @end smallexample @noindent -to avoid the macro expansion. Using the macro has two big adavantages: +to avoid the macro expansion. Using the macro has two big advantages: it is more portable and one does not have to choose the right function among @code{isnan}, @code{isnanf}, and @code{isnanl}. @end deftypefn @@ -297,7 +297,7 @@ among @code{isnan}, @code{isnanf}, and @code{isnanl}. @cindex decompose complex numbers This section lists functions performing some of the simple mathematical -operations on complex numbers. Using any of the function requries that +operations on complex numbers. Using any of the function requires that the C compiler understands the @code{complex} keyword, introduced to the C language in the @w{ISO C 9X} standard. @@ -357,7 +357,7 @@ cut along the negative real axis. @deftypefunx {complex long double} cprojl (complex long double @var{z}) Return the projection of the complex value @var{z} on the Riemann sphere. Values with a infinite complex part (even if the real part -is NaN) are projected to positive infinte on the real axis. If the real part is infinite, the result is equivalent to +is NaN) are projected to positive infinite on the real axis. If the real part is infinite, the result is equivalent to @smallexample INFINITY + I * copysign (0.0, cimag (z)) @@ -531,7 +531,7 @@ bit set. This is not the same as @code{x < 0.0} since in some floating-point formats (e.g., @w{IEEE 754}) the zero value is optionally signed. The comparison @code{-0.0 < 0.0} will not be true while @code{signbit -(-0.0)} will return a nonzeri value. +(-0.0)} will return a nonzero value. @end deftypefun @node Rounding and Remainders @@ -599,7 +599,7 @@ raise the inexact exception. @comment math.h @comment ISO @deftypefun double modf (double @var{value}, double *@var{integer-part}) -@deftypefunx float modff (flaot @var{value}, float *@var{integer-part}) +@deftypefunx float modff (float @var{value}, float *@var{integer-part}) @deftypefunx {long double} modfl (long double @var{value}, long double *@var{integer-part}) These functions break the argument @var{value} into an integer part and a fractional part (between @code{-1} and @code{1}, exclusive). Their sum @@ -1060,7 +1060,7 @@ format supports this; and to the largest representable value otherwise. If the input string is @code{"nan"} or @code{"nan(@var{n-char-sequence})"} the return value of @code{strtod} is the representation of the NaN (not a number) value (if the -flaoting-point formats supports this. The form with the +floating-point formats supports this. The form with the @var{n-char-sequence} enables in an implementation specific way to specify the form of the NaN value. When using the @w{IEEE 754} floating-point format, the NaN value can have a lot of forms since only diff --git a/manual/conf.texi b/manual/conf.texi index 64591ee9f2..86e29a8e04 100644 --- a/manual/conf.texi +++ b/manual/conf.texi @@ -1601,56 +1601,56 @@ after logging in. @comment unistd.h @comment Unix98 @item _CS_LFS_CFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the C compiler if a source is compiled using the @code{_LARGEFILE_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS_LDFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the linker if a source is compiled using the @code{_LARGEFILE_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS_LIBS -The returned string specifies which additionals libraries must be linked +The returned string specifies which additional libraries must be linked to the application if a source is compiled using the @code{_LARGEFILE_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS_LINTFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the the lint tool if a source is compiled using the @code{_LARGEFILE_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS64_CFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the C compiler if a source is compiled using the @code{_LARGEFILE64_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS64_LDFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the linker if a source is compiled using the @code{_LARGEFILE64_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS64_LIBS -The returned string specifies which additionals libraries must be linked +The returned string specifies which additional libraries must be linked to the application if a source is compiled using the @code{_LARGEFILE64_SOURCE} feature select macro; @pxref{Feature Test Macros}. @comment unistd.h @comment Unix98 @item _CS_LFS64_LINTFLAGS -The returned string specifies which additionals flags must be given to +The returned string specifies which additional flags must be given to the the lint tool if a source is compiled using the @code{_LARGEFILE64_SOURCE} feature select macro; @pxref{Feature Test Macros}. @end table diff --git a/manual/creature.texi b/manual/creature.texi index 2e0c62e1f7..38a11c0093 100644 --- a/manual/creature.texi +++ b/manual/creature.texi @@ -95,7 +95,7 @@ Single Unix specification, @w{version 2}. @comment X/Open @defvr Macro _LARGEFILE_SOURCE If this macro is defined some extra functions are available which -rectify a few shortcomings in all previous standards. More concreten +rectify a few shortcomings in all previous standards. More concrete the functions @code{fseeko} and @code{ftello} are available. Without these functions the difference between the @w{ISO C} interface (@code{fseek}, @code{ftell}) and the low-level POSIX interface diff --git a/manual/filesys.texi b/manual/filesys.texi index 7e8a1a12d2..6d62545cc4 100644 --- a/manual/filesys.texi +++ b/manual/filesys.texi @@ -18,7 +18,7 @@ access permissions and modification times. * Accessing Directories:: Finding out what files a directory contains. * Working on Directory Trees:: Apply actions to all files or a selectable - subset of a directory hierachy. + subset of a directory hierarchy. * Hard Links:: Adding alternate names to a file. * Symbolic Links:: A file that ``points to'' a file name. * Deleting Files:: How to delete a file, and what that means. @@ -504,14 +504,14 @@ we want to see all directory entries we always return @code{1}. @node Working on Directory Trees @section Working on Directory Trees -@cindex directory hierachy -@cindex hierachy, directory +@cindex directory hierarchy +@cindex hierarchy, directory @cindex tree, directory The functions to handle files in directories described so far allowed to retrieve all the information in small pieces or process all files in a directory (see @code{scandir}). Sometimes it is useful to process whole -hierachies of directories and the contained files. The X/Open +hierarchies of directories and the contained files. The X/Open specification define two functions to do this. The simpler form is derived from an early definition in @w{System V} systems and therefore this function is available on SVID derived systems. The prototypes and @@ -591,7 +591,7 @@ with some extra information as described below. @deftp {Data Type} {struct FTW} The contained information helps to interpret the name parameter and gives some information about current state of the traversal of the -directory hierachy. +directory hierarchy. @table @code @item int base @@ -644,7 +644,7 @@ The @var{descriptors} parameter to the @code{ftw} function specifies how many file descriptors the @code{ftw} function is allowed to consume. The more descriptors can be used the faster the function can run. For each level of directories at most one descriptor is used so that for -very deep directory hierachies the limit on open file descriptors for +very deep directory hierarchies the limit on open file descriptors for the process or the system can be exceeded. Beside this the limit on file descriptors is counted together for all threads in a multi-threaded program and therefore it is always good too limit the maximal number of @@ -679,7 +679,7 @@ values, combined using bitwise OR. While traversing the directory symbolic links are not followed. I.e., if this flag is given symbolic links are reported using the @code{FTW_SL} value for the type parameter to the callback function. -Please note that if this flag is used the appearence of @code{FTW_SL} in +Please note that if this flag is used the appearance of @code{FTW_SL} in a callback function does not mean the referenced file does not exist. To indicate this the extra value @code{FTW_SLN} exists. @item FTW_MOUNT @@ -1447,7 +1447,7 @@ This macro returns nonzero if the file is a symbolic link. This macro returns nonzero if the file is a socket. @xref{Sockets}. @end deftypefn -An alterate non-POSIX method of testing the file type is supported for +An alternate non-POSIX method of testing the file type is supported for compatibility with BSD. The mode can be bitwise ANDed with @code{S_IFMT} to extract the file type code, and compared to the appropriate type code constant. For example, @@ -1780,7 +1780,7 @@ used as the swap area of diskless client machines. The idea is that the pages of the file will be cached in the client's memory, so it is a waste of the server's memory to cache them a second time. In this use the sticky bit also says that the filesystem may fail to record the -file's modification time onto disk reliably (the idea being that noone +file's modification time onto disk reliably (the idea being that no-one cares for a swap file). @end table @@ -1790,7 +1790,7 @@ These bit values are correct for most systems, but they are not guaranteed. @strong{Warning:} Writing explicit numbers for file permissions is bad -practice. It is not only nonportable, it also requires everyone who +practice. It is not only non-portable, it also requires everyone who reads your program to remember what the bits mean. To make your program clean, use the symbolic names. @@ -2080,7 +2080,7 @@ Argument that means, test for existence of the file. @cindex file access time @cindex file modification time @cindex file attribute modification time -Each file has three timestamps associated with it: its access time, +Each file has three time stamps associated with it: its access time, its modification time, and its attribute modification time. These correspond to the @code{st_atime}, @code{st_mtime}, and @code{st_ctime} members of the @code{stat} structure; see @ref{File Attributes}. @@ -2093,7 +2093,7 @@ values, see @ref{Calendar Time}. Reading from a file updates its access time attribute, and writing updates its modification time. When a file is created, all three -timestamps for that file are set to the current time. In addition, the +time stamps for that file are set to the current time. In addition, the attribute change time and modification time fields of the directory that contains the new entry are updated. @@ -2109,7 +2109,7 @@ the times for the file being renamed. Changing attributes of a file (for example, with @code{chmod}) updates its attribute change time field. -You can also change some of the timestamps of a file explicitly using +You can also change some of the time stamps of a file explicitly using the @code{utime} function---all except the attribute change time. You need to include the header file @file{utime.h} to use this facility. @pindex utime.h @@ -2142,7 +2142,7 @@ values from the @code{actime} and @code{modtime} members (respectively) of the @code{utimbuf} structure pointed at by @var{times}. The attribute modification time for the file is set to the current time -in either case (since changing the timestamps is itself a modification +in either case (since changing the time stamps is itself a modification of the file attributes). The @code{utime} function returns @code{0} if successful and @code{-1} @@ -2153,7 +2153,7 @@ are defined for this function: @table @code @item EACCES There is a permission problem in the case where a null pointer was -passed as the @var{times} argument. In order to update the timestamp on +passed as the @var{times} argument. In order to update the time stamp on the file, you must either be the owner of the file, have write permission on the file, or be a privileged user. diff --git a/manual/intro.texi b/manual/intro.texi index 7597807274..fa16041b9b 100644 --- a/manual/intro.texi +++ b/manual/intro.texi @@ -15,7 +15,7 @@ operating system, and extensions specific to the GNU system. The purpose of this manual is to tell you how to use the facilities of the GNU library. We have mentioned which features belong to which -standards to help you identify things that are potentially nonportable +standards to help you identify things that are potentially non-portable to other systems. But the emphasis in this manual is not on strict portability. diff --git a/manual/llio.texi b/manual/llio.texi index 23c5f767f1..c31a5cf0eb 100644 --- a/manual/llio.texi +++ b/manual/llio.texi @@ -242,7 +242,7 @@ extra bytes are stripped of. If the file was small or equal to @var{length} in size before nothing is done. The file must be writable by the user to perform this operation. -The return value is zero is everything wnet ok. Otherwise the return +The return value is zero is everything went ok. Otherwise the return value is @math{-1} and the global variable @var{errno} is set to: @table @code @item EACCES @@ -1180,16 +1180,16 @@ No synchronization is possible since the system does not implement this. Sometimes it is not even necessary to write all data associated with a file descriptor. E.g., in database files which do not change in size it is enough to write all the file content data to the device. -Metainformation like the modification time etc. are not that important +Meta-information like the modification time etc. are not that important and leaving such information uncommitted does not prevent a successful recovering of the file in case of a problem. @comment unistd.h @comment POSIX @deftypefun int fdatasync (int @var{fildes}) -When a call to the @code{fdatasync} function returns it is maed sure +When a call to the @code{fdatasync} function returns it is made sure that all of the file data is written to the device. For all pending I/O -operations the parts guaranteeing data integrety finished. +operations the parts guaranteeing data integrity finished. Not all systems implement the @code{fdatasync} operation. On systems missing this functionality @code{fdatasync} is emulated by a call to diff --git a/manual/maint.texi b/manual/maint.texi index e6fc47f8e1..7698549bf3 100644 --- a/manual/maint.texi +++ b/manual/maint.texi @@ -513,25 +513,35 @@ posix @noindent So the final list is @file{unix/bsd/vax unix/bsd unix/inet unix posix}. -@file{sysdeps} has two ``special'' subdirectories, called @file{generic} -and @file{stub}. These two are always implicitly appended to the list -of subdirectories (in that order), so you needn't put them in an -@file{Implies} file, and you should not create any subdirectories under -them intended to be new specific categories. @file{generic} is for -things that can be implemented in machine-independent C, using only -other machine-independent functions in the C library. @file{stub} is -for @dfn{stub} versions of functions which cannot be implemented on a -particular machine or operating system. The stub functions always -return an error, and set @code{errno} to @code{ENOSYS} (Function not -implemented). @xref{Error Reporting}. - -A source file is known to be system-dependent by its having a version in -@file{generic} or @file{stub}; every generally-available function whose -implementation is system-dependent in should have either a generic or -stub implementation (there is no point in having both). Some rare functions -are only useful on specific systems and aren't defined at all on others; -these do not appear anywhere in the system-independent source code or makefiles -(including the @file{generic} and @file{stub} directories), only in the +@file{sysdeps} has a ``special'' subdirectory called @file{generic}. It +is always implicitly appended to the list of subdirectories, so you +needn't put it in an @file{Implies} file, and you should not create any +subdirectories under it intended to be new specific categories. +@file{generic} serves two purposes. First, the makefiles do not bother +to look for a system-dependent version of a file that's not in +@file{generic}. This means that any system-dependent source file must +have an analogue in @file{generic}, even if the routines defined by that +file are not implemented on other platforms. Second. the @file{generic} +version of a system-dependent file is used if the makefiles do not find +a version specific to the system you're compiling for. + +If it is possible to implement the routines in a @file{generic} file in +machine-independent C, using only other machine-independent functions in +the C library, then you should do so. Otherwise, make them stubs. A +@dfn{stub} function is a function which cannot be implemented on a +particular machine or operating system. Stub functions always return an +error, and set @code{errno} to @code{ENOSYS} (Function not implemented). +@xref{Error Reporting}. If you define a stub function, you must place +the statement @code{stub_warning(@var{function})}, where @var{function} +is the name of your function, after its definition; also, you must +include the file @code{<stub-tag.h>} into your file. This causes the +function to be listed in the installed @code{<gnu/stubs.h>}, and +makes GNU ld warn when the function is used. + +Some rare functions are only useful on specific systems and aren't +defined at all on others; these do not appear anywhere in the +system-independent source code or makefiles (including the +@file{generic} and @file{stub} directories), only in the system-dependent @file{Makefile} in the specific system's subdirectory. If you come across a file that is in one of the main source directories @@ -737,8 +747,7 @@ hierarchy that are not for particular machine architectures. @table @file @item generic -@itemx stub -As described above (@pxref{Porting}), these are the two subdirectories +As described above (@pxref{Porting}), this is the subdirectory that every configuration implicitly uses after all others. @item ieee754 diff --git a/manual/math.texi b/manual/math.texi index fe9394b22d..478678f236 100644 --- a/manual/math.texi +++ b/manual/math.texi @@ -236,7 +236,7 @@ If the exception does not cause a trap handler to be called the result of the operation is taken as a quiet NaN. @item Division by Zero -This exception is raised if the devisor is zero and the dividend is a +This exception is raised if the divisor is zero and the dividend is a finite nonzero number. If no trap occurs the result is either @math{+@infinity{}} or @math{-@infinity{}}, depending on the signs of the operands. @@ -413,7 +413,7 @@ representable as an integer. These are completely independent types. It is sometimes necessary so save the complete status of the floating-point unit for a certain time to perform some completely different actions. Beside the status of the exception flags, the -control word for the exceptions and the rounding mode can be safed. +control word for the exceptions and the rounding mode can be saved. The file @file{fenv.h} defines the type @code{fenv_t}. The layout of a variable of this type is implementation defined but the variable is able @@ -710,7 +710,7 @@ exception if one of the arguments is an unordered value. @cindex Optimization If an application uses many floating point function it is often the case -that the costs for the function calls itseld are not neglectable. +that the costs for the function calls itselfs are not neglectable. Modern processor implementation often can execute the operation itself very fast but the call means a disturbance of the |