diff options
author | Ondřej Bílka <neleai@seznam.cz> | 2015-07-12 11:32:56 +0200 |
---|---|---|
committer | Ondřej Bílka <neleai@seznam.cz> | 2015-08-20 09:43:50 +0200 |
commit | 9ceeb279314a9b76679044749bd98aa817006bd1 (patch) | |
tree | 8e35a5205b0e2a800b463cc3796fccc763ea0453 /manual/llio.texi | |
parent | cd4e69ed3e4b2d51ebd3dfaa0730793cf913de77 (diff) | |
download | glibc-9ceeb279314a9b76679044749bd98aa817006bd1.tar.gz glibc-9ceeb279314a9b76679044749bd98aa817006bd1.tar.xz glibc-9ceeb279314a9b76679044749bd98aa817006bd1.zip |
Fix exponents in manual.
* manual/macros.texi: Add twoexp macro. * manual/filesys.texi: Fix exponents. * manual/llio.texi: Likewise. * manual/stdio.texi: Likewise.
Diffstat (limited to 'manual/llio.texi')
-rw-r--r-- | manual/llio.texi | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/manual/llio.texi b/manual/llio.texi index 4f3fada1e7..019dea2c31 100644 --- a/manual/llio.texi +++ b/manual/llio.texi @@ -150,8 +150,8 @@ or @code{O_CREAT} is set and the file does not already exist. If on a 32 bit machine the sources are translated with @code{_FILE_OFFSET_BITS == 64} the function @code{open} returns a file descriptor opened in the large file mode which enables the file handling -functions to use files up to @math{2^63} bytes in size and offset from -@math{-2^63} to @math{2^63}. This happens transparently for the user +functions to use files up to @twoexp{63} bytes in size and offset from +@minus{}@twoexp{63} to @twoexp{63}. This happens transparently for the user since all of the lowlevel file handling functions are equally replaced. This function is a cancellation point in multi-threaded programs. This @@ -201,8 +201,8 @@ open (@var{filename}, O_WRONLY | O_CREAT | O_TRUNC, @var{mode}) If on a 32 bit machine the sources are translated with @code{_FILE_OFFSET_BITS == 64} the function @code{creat} returns a file descriptor opened in the large file mode which enables the file handling -functions to use files up to @math{2^63} in size and offset from -@math{-2^63} to @math{2^63}. This happens transparently for the user +functions to use files up to @twoexp{63} in size and offset from +@minus{}@twoexp{63} to @twoexp{63}. This happens transparently for the user since all of the lowlevel file handling functions are equally replaced. @end deftypefn @@ -422,7 +422,7 @@ not affected by the operation. The value is the same as before the call. When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the @code{pread} function is in fact @code{pread64} and the type @code{off_t} has 64 bits, which makes it possible to handle files up to -@math{2^63} bytes in length. +@twoexp{63} bytes in length. The return value of @code{pread} describes the number of bytes read. In the error case it returns @math{-1} like @code{read} does and the @@ -451,7 +451,7 @@ version 2. This function is similar to the @code{pread} function. The difference is that the @var{offset} parameter is of type @code{off64_t} instead of @code{off_t} which makes it possible on 32 bit machines to address -files larger than @math{2^31} bytes and up to @math{2^63} bytes. The +files larger than @twoexp{31} bytes and up to @twoexp{63} bytes. The file descriptor @code{filedes} must be opened using @code{open64} since otherwise the large offsets possible with @code{off64_t} will lead to errors with a descriptor in small file mode. @@ -623,7 +623,7 @@ not affected by the operation. The value is the same as before the call. When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the @code{pwrite} function is in fact @code{pwrite64} and the type @code{off_t} has 64 bits, which makes it possible to handle files up to -@math{2^63} bytes in length. +@twoexp{63} bytes in length. The return value of @code{pwrite} describes the number of written bytes. In the error case it returns @math{-1} like @code{write} does and the @@ -652,7 +652,7 @@ version 2. This function is similar to the @code{pwrite} function. The difference is that the @var{offset} parameter is of type @code{off64_t} instead of @code{off_t} which makes it possible on 32 bit machines to address -files larger than @math{2^31} bytes and up to @math{2^63} bytes. The +files larger than @twoexp{31} bytes and up to @twoexp{63} bytes. The file descriptor @code{filedes} must be opened using @code{open64} since otherwise the large offsets possible with @code{off64_t} will lead to errors with a descriptor in small file mode. @@ -752,7 +752,7 @@ only for pipes and FIFOs, but on @gnusystems{}, you always get When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the @code{lseek} function is in fact @code{lseek64} and the type @code{off_t} has 64 bits which makes it possible to handle files up to -@math{2^63} bytes in length. +@twoexp{63} bytes in length. This function is a cancellation point in multi-threaded programs. This is a problem if the thread allocates some resources (like memory, file @@ -775,7 +775,7 @@ descriptors. This function is similar to the @code{lseek} function. The difference is that the @var{offset} parameter is of type @code{off64_t} instead of @code{off_t} which makes it possible on 32 bit machines to address -files larger than @math{2^31} bytes and up to @math{2^63} bytes. The +files larger than @twoexp{31} bytes and up to @twoexp{63} bytes. The file descriptor @code{filedes} must be opened using @code{open64} since otherwise the large offsets possible with @code{off64_t} will lead to errors with a descriptor in small file mode. @@ -848,7 +848,7 @@ is transparently replaced by @code{off64_t}. This type is used similar to @code{off_t}. The difference is that even on 32 bit machines, where the @code{off_t} type would have 32 bits, @code{off64_t} has 64 bits and so is able to address files up to -@math{2^63} bytes in length. +@twoexp{63} bytes in length. When compiling with @code{_FILE_OFFSET_BITS == 64} this type is available under the name @code{off_t}. |