aboutsummaryrefslogtreecommitdiff
path: root/manual/creature.texi
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.de>2000-03-10 08:41:39 +0000
committerAndreas Jaeger <aj@suse.de>2000-03-10 08:41:39 +0000
commite8b1163ed03e17558e918116b2ab594a60161154 (patch)
tree79aa1e06f5a24d3fa6d23c007cf141aacaf4d4f0 /manual/creature.texi
parentf25da8d01f8d783fff627a95628a73b037526245 (diff)
downloadglibc-e8b1163ed03e17558e918116b2ab594a60161154.zip
glibc-e8b1163ed03e17558e918116b2ab594a60161154.tar.gz
glibc-e8b1163ed03e17558e918116b2ab594a60161154.tar.bz2
2000-03-09 Martin Buchholz <martin@xemacs.org>
* sysdeps/unix/sysv/linux/alpha/syscall.S: * manual/message.texi (Using gettextized software): * manual/message.texi (Message Translation): Doc Fixes. * manual/filesys.texi (File Size): * manual/charset.texi (glibc iconv Implementation): * locale/programs/ld-collate.c (collate_output): * iconv/gconv_db.c (find_derivation): * manual/install.texi: * manual/search.texi (Hash Search Function): * manual/stdio.texi (Output Conversion Syntax): * FAQ.in: * config.h.in: * sysdeps/generic/dl-sysdep.c: Doc Fixes. `allows to' is not correct English. * elf/rtld.c: Doc fixes. * manual/creature.texi (Feature Test Macros): Doc fixes. * manual/memory.texi (Hooks for Malloc): Doc Fixes. * manual/filesys.texi (Working Directory): Check for ERANGE to avoid infloop.
Diffstat (limited to 'manual/creature.texi')
-rw-r--r--manual/creature.texi22
1 files changed, 11 insertions, 11 deletions
diff --git a/manual/creature.texi b/manual/creature.texi
index bb7f730..56acf97 100644
--- a/manual/creature.texi
+++ b/manual/creature.texi
@@ -148,15 +148,15 @@ This macro was introduced as part of the Large File Support extension (LFS).
@comment (NONE)
@comment X/Open
@defvr Macro _LARGEFILE64_SOURCE
-If you define this macro an additional set of function gets available
-which enables to use on @w{32 bit} systems to use files of sizes beyond
+If you define this macro an additional set of function is made available
+which enables @w{32 bit} systems to use files of sizes beyond
the usual limit of 2GB. This interface is not available if the system
does not support files that large. On systems where the natural file
size limit is greater than 2GB (i.e., on @w{64 bit} systems) the new
functions are identical to the replaced functions.
The new functionality is made available by a new set of types and
-functions which replace existing. The names of these new objects
+functions which replace the existing ones. The names of these new objects
contain @code{64} to indicate the intention, e.g., @code{off_t}
vs. @code{off64_t} and @code{fseeko} vs. @code{fseeko64}.
@@ -168,18 +168,18 @@ not generally used (see @code{_FILE_OFFSET_BITS}.
@comment (NONE)
@comment X/Open
@defvr Macro _FILE_OFFSET_BITS
-This macro lets decide which file system interface shall be used, one
+This macro determines which file system interface shall be used, one
replacing the other. While @code{_LARGEFILE64_SOURCE} makes the @w{64
bit} interface available as an additional interface
-@code{_FILE_OFFSET_BITS} allows to use the @w{64 bit} interface to
+@code{_FILE_OFFSET_BITS} allows the @w{64 bit} interface to
replace the old interface.
-If @code{_FILE_OFFSET_BITS} is undefined or if it is defined to the
-value @code{32} nothing changes. The @w{32 bit} interface is used and
+If @code{_FILE_OFFSET_BITS} is undefined, or if it is defined to the
+value @code{32}, nothing changes. The @w{32 bit} interface is used and
types like @code{off_t} have a size of @w{32 bits} on @w{32 bit}
systems.
-If the macro is defined to the value @code{64} the large file interface
+If the macro is defined to the value @code{64}, the large file interface
replaces the old interface. I.e., the functions are not made available
under different names as @code{_LARGEFILE64_SOURCE} does. Instead the
old function names now reference the new functions, e.g., a call to
@@ -233,10 +233,10 @@ get very strange errors at run time.
If you define one of these macros, reentrant versions of several functions get
declared. Some of the functions are specified in POSIX.1c but many others
are only available on a few other systems or are unique to GNU libc.
-The problem is that the standardization of the thread safe C library
-interface still is behind.
+The problem is the delay in the standardization of the thread safe C library
+interface.
-Unlike on some other systems no special version of the C library must be
+Unlike on some other systems, no special version of the C library must be
used for linking. There is only one version but while compiling this
it must have been specified to compile as thread safe.
@end defvr