* m4/stdint.m4 (gl_STDINT_H): Set STDINT_H to empty if stdint.h

[gnulib.git] / doc / functions.texi

diff --git a/doc/functions.texi b/doc/functions.texi
index c9be919..f89a7f8 100644 (file)
--- a/doc/functions.texi
+++ b/doc/functions.texi
@@ -2,6 +2,15 @@
 @section Portability of Standard Functions
 @cindex functions
 
+@c Copyright (C) 2006 Free Software Foundation, Inc.
+
+@c Permission is granted to copy, distribute and/or modify this document
+@c under the terms of the GNU Free Documentation License, Version 1.2 or
+@c any later version published by the Free Software Foundation; with no
+@c Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+@c Texts.  A copy of the license is included in the ``GNU Free
+@c Documentation License'' file as part of this distribution.
+
 Many standard library functions have portability limitations, although
 they are specified in the
 @uref{http://www.opengroup.org/susv3, Posix standard}.  In this section,
@@ -143,8 +152,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item fputc
 @itemx fputs
@@ -237,7 +247,7 @@ If the given buffer is too small for the host name, some implementations
 fail with @code{EINVAL}, instead of returning a truncated host name.
 
 @item getopt
-The default behaviour of the glibc implementation of @code{getopt} allows
+The default behavior of the glibc implementation of @code{getopt} allows
 mixing option and non-option arguments on the command line in any order.
 Other implementations, such as the one in Cygwin, enforce strict POSIX
 compliance: they require that the option arguments precede the non-option
@@ -456,8 +466,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item pthread_create
 On Linux/glibc systems before the advent of NPTL, signals could only be
@@ -588,7 +599,7 @@ void handle_child (int sigchld)
 except that @code{SIG_IGN} for @code{SIGCHLD} has the effect that the children
 execution times are not accounted in the @code{times} function.
 On some systems (BSD? SystemV? Linux?), you need to use the @code{sigaction}
-flag @code{SA_NOCLDWAIT} in order to obtain this behaviour.
+flag @code{SA_NOCLDWAIT} in order to obtain this behavior.
 
 @item sigaltstack
 @code{sigaltstack} doesn't work on HP-UX 11/IA-64 and OpenBSD 3.6/Sparc64.
@@ -601,7 +612,7 @@ if the signal is triggered twice and the signal handler was not quick enough
 reinstalling itself as a handler.  On BSD systems and glibc systems, on the
 other hand, when the signal is triggered, the kernel blocks the signal
 before invoking the handler.  This is saner, but POSIX still allows either
-behaviour.  To avoid this problem, use @code{sigaction} instead of
+behavior.  To avoid this problem, use @code{sigaction} instead of
 @code{signal}.
 
 @item sigtimedwait
@@ -625,8 +636,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item socket
 On BeOS, the descriptors returned by the @code{socket} function can not be used
@@ -639,8 +651,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item sscanf
 On Windows systems (excluding Cygwin), this function does not set @code{errno}
@@ -777,8 +790,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines this function so that
 it is POSIX compliant.
 
-On Windows, this function doesn't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item vfscanf
 On Windows systems (excluding Cygwin), this function does not set @code{errno}
@@ -795,8 +809,9 @@ access arguments in an arbitrary order, such as @code{"%2$s"}.  The fix is to
 include @file{<libintl.h>} from GNU gettext; it redefines these functions so
 that they are POSIX compliant.
 
-On Windows, these functions don't support the @code{'} flag and the @code{hh},
-@code{ll}, @code{j}, @code{t}, @code{z} size specifiers.
+On Windows systems (excluding Cygwin), this function doesn't support
+the @code{'} flag and the @code{hh}, @code{ll}, @code{j}, @code{t},
+@code{z} size specifiers.
 
 @item vscanf
 @item vsscanf