* doc/c-ctype.texi: Change '.' to '@.' where appropriate.
* doc/glibc-functions/fstatfs.texi: Likewise.
* doc/glibc-functions/fts_children.texi: Likewise.
* doc/glibc-functions/fts_read.texi: Likewise.
* doc/glibc-functions/getdirentries.texi: Likewise.
* doc/glibc-functions/mkostemp.texi: Likewise.
* doc/glibc-functions/mkostemps.texi: Likewise.
* doc/glibc-functions/mkstemps.texi: Likewise.
* doc/glibc-functions/preadv.texi: Likewise.
* doc/glibc-functions/pwritev.texi: Likewise.
* doc/glibc-functions/sendfile.texi: Likewise.
* doc/glibc-functions/statfs.texi: Likewise.
* doc/gnulib-intro.texi: Likewise.
* doc/gnulib-tool.texi: Likewise.
* doc/intprops.texi: Likewise.
* doc/lib-symbol-visibility.texi: Likewise.
* doc/licenses-texi.texi: Likewise.
* doc/pastposix-functions/bcmp.texi: Likewise.
* doc/pastposix-functions/bcopy.texi: Likewise.
* doc/pastposix-functions/bzero.texi: Likewise.
* doc/pastposix-functions/ecvt.texi: Likewise.
* doc/pastposix-functions/fcvt.texi: Likewise.
* doc/pastposix-functions/ftime.texi: Likewise.
* doc/pastposix-functions/gcvt.texi: Likewise.
* doc/pastposix-functions/getwd.texi: Likewise.
* doc/pastposix-functions/index.texi: Likewise.
* doc/pastposix-functions/mktemp.texi: Likewise.
* doc/pastposix-functions/rindex.texi: Likewise.
* doc/pastposix-functions/wcswcs.texi: Likewise.
* doc/posix-functions/aio_cancel.texi: Likewise.
* doc/posix-functions/aio_error.texi: Likewise.
* doc/posix-functions/aio_fsync.texi: Likewise.
* doc/posix-functions/aio_read.texi: Likewise.
* doc/posix-functions/aio_return.texi: Likewise.
* doc/posix-functions/aio_suspend.texi: Likewise.
* doc/posix-functions/aio_write.texi: Likewise.
* doc/posix-functions/creat.texi: Likewise.
* doc/posix-functions/ctime.texi: Likewise.
* doc/posix-functions/daylight.texi: Likewise.
* doc/posix-functions/fgetpos.texi: Likewise.
* doc/posix-functions/fopen.texi: Likewise.
* doc/posix-functions/freopen.texi: Likewise.
* doc/posix-functions/fseeko.texi: Likewise.
* doc/posix-functions/fsetpos.texi: Likewise.
* doc/posix-functions/fstatat.texi: Likewise.
* doc/posix-functions/fstatvfs.texi: Likewise.
* doc/posix-functions/ftello.texi: Likewise.
* doc/posix-functions/ftruncate.texi: Likewise.
* doc/posix-functions/getrlimit.texi: Likewise.
* doc/posix-functions/lio_listio.texi: Likewise.
* doc/posix-functions/localtime.texi: Likewise.
* doc/posix-functions/lseek.texi: Likewise.
* doc/posix-functions/mkstemp.texi: Likewise.
* doc/posix-functions/mktime.texi: Likewise.
* doc/posix-functions/open.texi: Likewise.
* doc/posix-functions/openat.texi: Likewise.
* doc/posix-functions/opendir.texi: Likewise.
* doc/posix-functions/pread.texi: Likewise.
* doc/posix-functions/pwrite.texi: Likewise.
* doc/posix-functions/readdir.texi: Likewise.
* doc/posix-functions/readdir_r.texi: Likewise.
* doc/posix-functions/scandir.texi: Likewise.
* doc/posix-functions/seekdir.texi: Likewise.
* doc/posix-functions/setrlimit.texi: Likewise.
* doc/posix-functions/statvfs.texi: Likewise.
* doc/posix-functions/strftime.texi: Likewise.
* doc/posix-functions/telldir.texi: Likewise.
* doc/posix-functions/timezone.texi: Likewise.
* doc/posix-functions/tmpfile.texi: Likewise.
* doc/posix-functions/truncate.texi: Likewise.
* doc/posix-functions/tzname.texi: Likewise.
* doc/posix-functions/wcsftime.texi: Likewise.
* doc/windows-sockets.texi: Likewise.
+2020-06-01 Asher Gordon <AsDaGo@posteo.net>
+
+ doc: Change '.' to '@.' where appropriate.
+ * doc/c-ctype.texi: Change '.' to '@.' where appropriate.
+ * doc/glibc-functions/fstatfs.texi: Likewise.
+ * doc/glibc-functions/fts_children.texi: Likewise.
+ * doc/glibc-functions/fts_read.texi: Likewise.
+ * doc/glibc-functions/getdirentries.texi: Likewise.
+ * doc/glibc-functions/mkostemp.texi: Likewise.
+ * doc/glibc-functions/mkostemps.texi: Likewise.
+ * doc/glibc-functions/mkstemps.texi: Likewise.
+ * doc/glibc-functions/preadv.texi: Likewise.
+ * doc/glibc-functions/pwritev.texi: Likewise.
+ * doc/glibc-functions/sendfile.texi: Likewise.
+ * doc/glibc-functions/statfs.texi: Likewise.
+ * doc/gnulib-intro.texi: Likewise.
+ * doc/gnulib-tool.texi: Likewise.
+ * doc/intprops.texi: Likewise.
+ * doc/lib-symbol-visibility.texi: Likewise.
+ * doc/licenses-texi.texi: Likewise.
+ * doc/pastposix-functions/bcmp.texi: Likewise.
+ * doc/pastposix-functions/bcopy.texi: Likewise.
+ * doc/pastposix-functions/bzero.texi: Likewise.
+ * doc/pastposix-functions/ecvt.texi: Likewise.
+ * doc/pastposix-functions/fcvt.texi: Likewise.
+ * doc/pastposix-functions/ftime.texi: Likewise.
+ * doc/pastposix-functions/gcvt.texi: Likewise.
+ * doc/pastposix-functions/getwd.texi: Likewise.
+ * doc/pastposix-functions/index.texi: Likewise.
+ * doc/pastposix-functions/mktemp.texi: Likewise.
+ * doc/pastposix-functions/rindex.texi: Likewise.
+ * doc/pastposix-functions/wcswcs.texi: Likewise.
+ * doc/posix-functions/aio_cancel.texi: Likewise.
+ * doc/posix-functions/aio_error.texi: Likewise.
+ * doc/posix-functions/aio_fsync.texi: Likewise.
+ * doc/posix-functions/aio_read.texi: Likewise.
+ * doc/posix-functions/aio_return.texi: Likewise.
+ * doc/posix-functions/aio_suspend.texi: Likewise.
+ * doc/posix-functions/aio_write.texi: Likewise.
+ * doc/posix-functions/creat.texi: Likewise.
+ * doc/posix-functions/ctime.texi: Likewise.
+ * doc/posix-functions/daylight.texi: Likewise.
+ * doc/posix-functions/fgetpos.texi: Likewise.
+ * doc/posix-functions/fopen.texi: Likewise.
+ * doc/posix-functions/freopen.texi: Likewise.
+ * doc/posix-functions/fseeko.texi: Likewise.
+ * doc/posix-functions/fsetpos.texi: Likewise.
+ * doc/posix-functions/fstatat.texi: Likewise.
+ * doc/posix-functions/fstatvfs.texi: Likewise.
+ * doc/posix-functions/ftello.texi: Likewise.
+ * doc/posix-functions/ftruncate.texi: Likewise.
+ * doc/posix-functions/getrlimit.texi: Likewise.
+ * doc/posix-functions/lio_listio.texi: Likewise.
+ * doc/posix-functions/localtime.texi: Likewise.
+ * doc/posix-functions/lseek.texi: Likewise.
+ * doc/posix-functions/mkstemp.texi: Likewise.
+ * doc/posix-functions/mktime.texi: Likewise.
+ * doc/posix-functions/open.texi: Likewise.
+ * doc/posix-functions/openat.texi: Likewise.
+ * doc/posix-functions/opendir.texi: Likewise.
+ * doc/posix-functions/pread.texi: Likewise.
+ * doc/posix-functions/pwrite.texi: Likewise.
+ * doc/posix-functions/readdir.texi: Likewise.
+ * doc/posix-functions/readdir_r.texi: Likewise.
+ * doc/posix-functions/scandir.texi: Likewise.
+ * doc/posix-functions/seekdir.texi: Likewise.
+ * doc/posix-functions/setrlimit.texi: Likewise.
+ * doc/posix-functions/statvfs.texi: Likewise.
+ * doc/posix-functions/strftime.texi: Likewise.
+ * doc/posix-functions/telldir.texi: Likewise.
+ * doc/posix-functions/timezone.texi: Likewise.
+ * doc/posix-functions/tmpfile.texi: Likewise.
+ * doc/posix-functions/truncate.texi: Likewise.
+ * doc/posix-functions/tzname.texi: Likewise.
+ * doc/posix-functions/wcsftime.texi: Likewise.
+ * doc/windows-sockets.texi: Likewise.
+
2020-05-31 Paul Eggert <eggert@cs.ucla.edu>
getrandom-tests: do not assume GRND_RANDOM yields short read
The @code{c-ctype} module contains functions operating on single-byte
characters, like the functions in @code{<ctype.h>}, that operate as if the
-locale encoding was ASCII. (The "C" locale on many systems has the locale
+locale encoding was ASCII@. (The "C" locale on many systems has the locale
encoding "ASCII".)
The functions are:
@item
On platforms where @code{f_blocks} in @samp{struct statfs} is a 32-bit
value, this function may not work correctly on files systems larger than
-4 TiB. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
+4 TiB@. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
Mac OS X.
@end itemize
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
correctly report the size of files or block devices larger than 2 GB and
-may not work correctly on huge directories larger than 2 GB. Also, on
+may not work correctly on huge directories larger than 2 GB@. Also, on
platforms where @code{ino_t} is a 32-bit type, this function may report
inode numbers incorrectly. The fix is to use the @code{AC_SYS_LARGEFILE}
macro (only on Mac OS X systems).
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
correctly report the size of files or block devices larger than 2 GB and
-may not work correctly on huge directories larger than 2 GB. Also, on
+may not work correctly on huge directories larger than 2 GB@. Also, on
platforms where @code{ino_t} is a 32-bit type, this function may report
inode numbers incorrectly. The fix is to use the @code{AC_SYS_LARGEFILE}
macro (only on Mac OS X systems).
Minix 3.1.8, IRIX 6.5, Solaris 11.4, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. The fix is to use
+work correctly on huge directories larger than 2 GB@. The fix is to use
the @code{AC_SYS_LARGEFILE} macro.
@end itemize
Mac OS X 10.13.
@item
On platforms where @code{off_t} is a 32-bit type, @code{mkostemp} may not work
-correctly to create files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly to create files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
Mac OS X 10.13.
@item
On platforms where @code{off_t} is a 32-bit type, @code{mkostemps} may not work
-correctly to create files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly to create files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
Mac OS X 10.5.
@item
On platforms where @code{off_t} is a 32-bit type, @code{mkstemps} may not work
-correctly to create files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly to create files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
glibc 2.9, Mac OS X 10.5, FreeBSD 5.2.1, Minix 3.1.8, AIX 5.2, HP-UX 11.31, IRIX 6.5, Solaris 11.4, Cygwin, mingw, MSVC 14, Android 6.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
glibc 2.9, Mac OS X 10.5, FreeBSD 5.2.1, Minix 3.1.8, AIX 5.2, HP-UX 11.31, IRIX 6.5, Solaris 11.4, Cygwin, mingw, MSVC 14, Android 6.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 5.0, OpenBSD 3.8, Minix 3.1.8, AIX 5.1, IRIX 6.5, Solaris 11 2010-11, Cygwin, mingw, MSVC 14, Android 4.4.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
@item
On platforms where @code{f_blocks} in @samp{struct statfs} is a 32-bit
value, this function may not work correctly on files systems larger than
-4 TiB. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
+4 TiB@. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
Mac OS X.
@end itemize
glibc on kFreeBSD is rarely tested.
@end itemize
@item
-Mac OS X. In versions 10.13, it's occasionally tested. In version
+Mac OS X@. In versions 10.13, it's occasionally tested. In version
10.5, it's rarely tested.
@item
FreeBSD 11.0 or newer is occasionally tested.
@node Copyright
@section Copyright
-Most modules are under the GPL. Some, mostly modules which can
-reasonably be used in libraries, are under LGPL. The source files
+Most modules are under the GPL@. Some, mostly modules which can
+reasonably be used in libraries, are under LGPL@. The source files
always say "GPL", but the real license specification is in the module
description file. If the module description file says "GPL", it means
"GPLv3+" (GPLv3 or newer, at the licensee's choice); if it says "LGPL",
@item tests/
If a license statement is not present in a test module, the test files are
-under GPL. Even if the corresponding source module is under LGPL, this is
+under GPL@. Even if the corresponding source module is under LGPL, this is
not a problem, since compiled tests are not installed by ``make install''.
@item doc/
Keep in mind that when you submit patches to files in Gnulib, you should
license them under a compatible license. This means that sometimes the
contribution will have to be LGPL, if the original file is available
-under LGPL. You can find out about it by looking for a "License: LGPL"
+under LGPL@. You can find out about it by looking for a "License: LGPL"
information in the corresponding module description.
@node Steady Development
@item
In projects which customarily omit from their VCS all files that are
generated from other source files, none of these files and directories
-are added into the VCS. As described in @ref{Modified imports}, there
+are added into the VCS@. As described in @ref{Modified imports}, there
are two ways to keep track of options and module names that are passed
to @code{gnulib-tool}. The command for restoring the omitted files
depends on it:
suggested in Seacord R, The CERT C Secure Coding Standard (2009,
revised 2011), in its two sections
``@url{https://www.securecoding.cert.org/confluence/display/c/INT30-C.+Ensure+that+unsigned+integer+operations+do+not+wrap,
-INT30-C. Ensure that unsigned integer operations do not wrap}'' and
+INT30-C@. Ensure that unsigned integer operations do not wrap}'' and
``@url{https://www.securecoding.cert.org/confluence/display/c/INT32-C.+Ensure+that+operations+on+signed+integers+do+not+result+in+overflow,
-INT32-C. Ensure that operations on signed integers do not result in
+INT32-C@. Ensure that operations on signed integers do not result in
overflow}'', Gnulib's implementation was derived independently of
CERT's suggestions.
files that shall be exported.
This is perfect: It burdens the maintainer only for exported API, not
-for library-internal API. And it keeps the annotations in the source code.
+for library-internal API@. And it keeps the annotations in the source code.
@end itemize
GNU libtool's @option{-export-symbols} option implements the first approach.
present as a file in the top-level directory. This is true not only for
the release tarballs, but also in the VCS repository. The file is
typically named @samp{COPYING} for the GNU GPL, or @samp{COPYING.LIB} or
-@samp{COPYING.LESSER} for the GNU LGPL. The presence of this file
+@samp{COPYING.LESSER} for the GNU LGPL@. The presence of this file
fulfills a legal obligation; see
@url{https://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude}.
This function is missing on some platforms:
mingw, MSVC 14, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{memcmp}
+This function is marked as ``legacy'' in POSIX@. Better use @code{memcmp}
instead.
@end itemize
Portability problems not fixed by Gnulib:
@itemize
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{memcpy}
+This function is marked as ``legacy'' in POSIX@. Better use @code{memcpy}
or @code{memmove} instead.
@end itemize
This function is missing on some platforms:
mingw, MSVC 14, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{memset}
+This function is marked as ``legacy'' in POSIX@. Better use @code{memset}
instead.
@end itemize
This function is missing on some platforms:
FreeBSD 6.0, NetBSD 5.0, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{sprintf}
+This function is marked as ``legacy'' in POSIX@. Better use @code{sprintf}
instead.
@end itemize
This function is missing on some platforms:
FreeBSD 6.0, NetBSD 5.0, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{sprintf}
+This function is marked as ``legacy'' in POSIX@. Better use @code{sprintf}
instead.
@end itemize
On native Windows platforms (mingw, MSVC), this function works incorrectly
when the environment variable @code{TZ} has been set by Cygwin.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{gettimeofday}
+This function is marked as ``legacy'' in POSIX@. Better use @code{gettimeofday}
or @code{clock_gettime} instead, and use @code{ftime} only as a fallback for
portability to Windows platforms.
@end itemize
This function is missing on some platforms:
Mac OS X 10.5, FreeBSD 6.0, NetBSD 5.0, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{sprintf}
+This function is marked as ``legacy'' in POSIX@. Better use @code{sprintf}
instead.
@end itemize
The size of the buffer required for this function is not a compile-time
constant. Also, the function truncates a result that would be larger than
the minimum buffer size. For these reasons, this function is marked as
-``legacy'' in POSIX. Better use the @code{getcwd} function instead.
+``legacy'' in POSIX@. Better use the @code{getcwd} function instead.
@end itemize
This function is missing on some platforms:
mingw, MSVC 14, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{strchr}
+This function is marked as ``legacy'' in POSIX@. Better use @code{strchr}
instead.
@end itemize
@itemize
@item
This function is not appropriate for creating temporary files. (It has
-security risks.) Therefore it is marked as ``legacy'' in POSIX. Better use
+security risks.) Therefore it is marked as ``legacy'' in POSIX@. Better use
@code{mkstemp} instead.
@end itemize
This function is missing on some platforms:
mingw, MSVC 14, Android 9.0.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{strrchr}
+This function is marked as ``legacy'' in POSIX@. Better use @code{strrchr}
instead.
@end itemize
On Windows and 32-bit AIX platforms, @code{wchar_t} is a 16-bit type and therefore cannot
accommodate all Unicode characters.
@item
-This function is marked as ``legacy'' in POSIX. Better use @code{wcsstr}
+This function is marked as ``legacy'' in POSIX@. Better use @code{wcsstr}
instead.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, AIX 5.1, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
FreeBSD 6.0, NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, AIX 5.1, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, AIX 5.1, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, @code{creat} may not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function does not fail when the file name argument ends in a slash
and (without the slash) names a nonexistent file, on some platforms:
a re-entrant interface @code{ctime_r}.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
A more flexible function is @code{strftime}. However, note that it is
Cygwin, mingw.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
A more portable way of getting the UTC offset is to use
contains Unix line terminators (LF), on some platforms: mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
HP-UX 11.00, AIX 7.1, Solaris 9.
@item
On platforms where @code{off_t} is a 32-bit type, @code{fopen} may not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
On Windows platforms (excluding Cygwin), this function does usually not
recognize the @file{/dev/null} filename.
the file: glibc 2.24.
@item
On platforms where @code{off_t} is a 32-bit type, @code{freopen} may not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
On Windows platforms (excluding Cygwin), this function does usually not
recognize the @file{/dev/null} filename.
This function fails on seekable stdin, stdout, and stderr: cygwin <= 1.5.24.
@item
On platforms where @code{off_t} is a 32-bit type, @code{fseeko} does not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
@itemize
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
@item
On platforms where @code{off_t} is a 32-bit type, @code{fstatat} may
not correctly report the size of files or block devices larger than 2
-GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
On some platforms, @code{fstatat(fd,"file/",buf,flag)} succeeds instead of
failing with @code{ENOTDIR}.
@item
On platforms where @code{f_blocks} in @samp{struct statvfs} is a 32-bit
value, this function may not work correctly on files systems larger than
-4 TiB. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
+4 TiB@. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
glibc/Hurd, HP-UX 11, Solaris.
@end itemize
This function fails on seekable stdin, stdout, and stderr: cygwin <= 1.5.24.
@item
On platforms where @code{off_t} is a 32-bit type, @code{ftello} does not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function is not
-applicable to arbitrary lengths for files larger than 2 GB. The fix is to
+applicable to arbitrary lengths for files larger than 2 GB@. The fix is to
use the @code{AC_SYS_LARGEFILE} macro.
@end itemize
mingw, MSVC 14.
@item
On platforms where @code{rlim_t} is a 32-bit type, this function does not
-allow to retrieve limits larger than 4 GB, such as for RLIMIT_FSIZE. The
+allow to retrieve limits larger than 4 GB, such as for RLIMIT_FSIZE@. The
fix is to use the @code{AC_SYS_LARGEFILE} macro.
@end itemize
NetBSD 3.0, OpenBSD 3.8, Minix 3.1.8, Cygwin, mingw, MSVC 14, Android 9.0.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. The fix is to use the
+work correctly on files larger than 2 GB@. The fix is to use the
@code{AC_SYS_LARGEFILE} macro.
@end itemize
FreeBSD 10.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
@itemize
@item
On platforms where @code{off_t} is a 32-bit type, @code{lseek} does not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function mistakenly succeeds on pipes on some platforms: mingw, MSVC 14.
@end itemize
mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, @code{mkstemp} may not work
-correctly to create files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly to create files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
On some older platforms, @code{mkstemp} can create a world or group
writable or readable file, if you haven't set the process umask to
@itemize
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
Mac OS X 10.5, FreeBSD 6.0, NetBSD 5.0, OpenBSD 3.8, Minix 3.1.8, AIX 5.1, HP-UX 11, IRIX 6.5, Solaris 10, Cygwin, mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, @code{open} may not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function does not fail when the file name argument ends in a slash
and (without the slash) names a nonexistent file or a file that is not a
AIX 7.1, Solaris 10.
@item
On platforms where @code{off_t} is a 32-bit type, @code{open} may not work
-correctly with files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly with files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function does not fail when the file name argument ends in a slash
and (without the slash) names a nonexistent file or a file that is not a
MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. Also, on platforms
+work correctly on huge directories larger than 2 GB@. Also, on platforms
where @code{ino_t} is a 32-bit type, this function may report inode numbers
incorrectly. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+work correctly on files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function returns zero instead of positive values when large file support
is enabled on some platforms:
mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+work correctly on files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@item
This function does not fail when an invalid (negative) offset is passed when
large file support is enabled on some platforms:
MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. Also, on platforms
+work correctly on huge directories larger than 2 GB@. Also, on platforms
where @code{ino_t} is a 32-bit type, this function may report inode numbers
incorrectly. This can occur with file systems such as XFS (typically on
-large disks) and NFS. (Cf. @code{AC_SYS_LARGEFILE}.)
+large disks) and NFS@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
Minix 3.1.8, mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. Also, on platforms
+work correctly on huge directories larger than 2 GB@. Also, on platforms
where @code{ino_t} is a 32-bit type, this function may report inode numbers
incorrectly. This can occur with file systems such as XFS (typically on
-large disks) and NFS. The fix is to use the @code{AC_SYS_LARGEFILE} macro.
+large disks) and NFS@. The fix is to use the @code{AC_SYS_LARGEFILE} macro.
@end itemize
Minix 3.1.8, Solaris 9, mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. Also, on platforms
+work correctly on huge directories larger than 2 GB@. Also, on platforms
where @code{ino_t} is a 32-bit type, this function may report inode numbers
incorrectly. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
MSVC 14, Android 5.1.
@item
On platforms where @code{long int} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. The fix is to use
+work correctly on huge directories larger than 2 GB@. The fix is to use
the @code{AC_SYS_LARGEFILE} macro (only on Mac OS X systems).
@end itemize
Minix 3.1.8, mingw, MSVC 14.
@item
On platforms where @code{rlim_t} is a 32-bit type, this function does not
-allow to set limits larger than 4 GB, such as for RLIMIT_FSIZE. The fix is
+allow to set limits larger than 4 GB, such as for RLIMIT_FSIZE@. The fix is
to use the @code{AC_SYS_LARGEFILE} macro.
@end itemize
@item
On platforms where @code{f_blocks} in @samp{struct statvfs} is a 32-bit
value, this function may not work correctly on files systems larger than
-4 TiB. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
+4 TiB@. The fix is to use the @code{AC_SYS_LARGEFILE} macro. This affects
glibc/Hurd, HP-UX 11, Solaris.
@end itemize
specifiers too, i.e., %C, %D, %h, %n, %r, %R, %t, and %T).
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
Extension: Gnulib offers a module @samp{nstrftime} that provides an
MSVC 14, Android 5.1.
@item
On platforms where @code{long int} is a 32-bit type, this function may not
-work correctly on huge directories larger than 2 GB. The fix is to use
+work correctly on huge directories larger than 2 GB@. The fix is to use
the @code{AC_SYS_LARGEFILE} macro (only on Mac OS X systems).
@end itemize
mingw.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
A more portable way of getting the UTC offset is to use
mingw, MSVC 14.
@item
On platforms where @code{off_t} is a 32-bit type, @code{tmpfile} may not work
-correctly to create files larger than 2 GB. (Cf. @code{AC_SYS_LARGEFILE}.)
+correctly to create files larger than 2 GB@. (Cf. @code{AC_SYS_LARGEFILE}.)
@end itemize
Portability problems not fixed by Gnulib:
mingw, MSVC 14, Android 4.4 with @code{AC_SYS_LARGEFILE} in effect.
@item
On platforms where @code{off_t} is a 32-bit type, this function is not
-applicable to arbitrary lengths for files larger than 2 GB. The fix is to
+applicable to arbitrary lengths for files larger than 2 GB@. The fix is to
use the @code{AC_SYS_LARGEFILE} macro.
@end itemize
Cygwin, mingw.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones supported by GNU or specified by POSIX. @xref{tzset}.
+zones supported by GNU or specified by POSIX@. @xref{tzset}.
@end itemize
A more portable way of getting the time zone abbreviation is to use
accommodate all Unicode characters.
@item
Native Windows platforms (mingw, MSVC) support only a subset of time
-zones specified by POSIX. @xref{tzset}.
+zones specified by POSIX@. @xref{tzset}.
@end itemize
other functions too.
The @code{getaddrinfo} function exists in @code{ws2tcpip.h} and @code{-lws2_32}
-on Windows XP. The function declaration is present if @code{WINVER >= 0x0501}.
+on Windows XP@. The function declaration is present if @code{WINVER >= 0x0501}.
Windows 2000 does not have @code{getaddrinfo} in its @file{WS2_32.DLL}.
Thus, if you want to assume Windows XP or later, you can add