Commit 2d365993 authored by Paul Eggert's avatar Paul Eggert
Browse files

Document wide integers better.

* files.texi (File Attributes):
ino_t values no longer map to anything larger than a single cons.
parent 201f31ae
......@@ -2,6 +2,8 @@
Document wide integers better.
* files.texi (File Attributes): Document ino_t values better.
ino_t values no longer map to anything larger than a single cons.
* numbers.texi (Integer Basics, Integer Basics, Arithmetic Operations):
(Bitwise Operations):
* objects.texi (Integer Type): Integers are typically 62 bits now.
......
......@@ -1237,13 +1237,9 @@ deleted and recreated; @code{nil} otherwise.
@item
The file's inode number. If possible, this is an integer. If the
inode number @math{N} is too large to be represented as an integer in
Emacs Lisp, but @math{N / 2^16} is representable, then the value has
the form @code{(@var{high} . @var{low})}, where @var{high} holds the
high bits (i.e., excluding the low-order bits) and @var{low} the low
16 bits. If the inode number is even larger, the value is of the form
@code{(@var{high} @var{middle} . @var{low})}, where @code{high} holds
the high bits, @var{middle} the next 24 bits, and @var{low} the low
16 bits.
Emacs Lisp, then the value has the form @code{(@var{high}
. @var{low})}, where @var{high} holds the high bits (i.e., all but the
low 16 bits) and @var{low} the low 16 bits.
@item
The filesystem number of the device that the file is on. Depending on
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment