Commit 39670ef4 authored by Paul Eggert's avatar Paul Eggert

* doc/lispref/internals.texi: Fix minor whitespace problems.

Fixes: debbugs:12973
parent 558fefa0
......@@ -324,7 +324,7 @@ provides @code{mallinfo} function.
@table @var
@item cons-size
Internal size of a cons cell, i.e.@: @code{sizeof (struct Lisp_Cons)}.
Internal size of a cons cell, i.e., @code{sizeof (struct Lisp_Cons)}.
@item used-conses
The number of cons cells in use.
......@@ -334,7 +334,7 @@ The number of cons cells for which space has been obtained from
the operating system, but that are not currently being used.
@item symbol-size
Internal size of a symbol, i.e.@: @code{sizeof (struct Lisp_Symbol)}.
Internal size of a symbol, i.e., @code{sizeof (struct Lisp_Symbol)}.
@item used-symbols
The number of symbols in use.
......@@ -344,7 +344,7 @@ The number of symbols for which space has been obtained from
the operating system, but that are not currently being used.
@item misc-size
Internal size of a miscellaneous entity, i.e.@:
Internal size of a miscellaneous entity, i.e.,
@code{sizeof (union Lisp_Misc)}, which is a size of the
largest type enumerated in @code{enum Lisp_Misc_Type}.
......@@ -357,7 +357,7 @@ The number of miscellaneous objects for which space has been obtained
from the operating system, but that are not currently being used.
@item string-size
Internal size of a string header, i.e.@: @code{sizeof (struct Lisp_String)}.
Internal size of a string header, i.e., @code{sizeof (struct Lisp_String)}.
@item used-strings
The number of string headers in use.
......@@ -373,7 +373,7 @@ This is used for convenience and equals to @code{sizeof (char)}.
The total size of all string data in bytes.
@item vector-size
Internal size of a vector header, i.e.@: @code{sizeof (struct Lisp_Vector)}.
Internal size of a vector header, i.e., @code{sizeof (struct Lisp_Vector)}.
@item used-vectors
The number of vector headers allocated from the vector blocks.
......@@ -388,7 +388,7 @@ The number of slots in all used vectors.
The number of free slots in all vector blocks.
@item float-size
Internal size of a float object, i.e.@: @code{sizeof (struct Lisp_Float)}.
Internal size of a float object, i.e., @code{sizeof (struct Lisp_Float)}.
(Do not confuse it with the native platform @code{float} or @code{double}.)
@item used-floats
......@@ -399,7 +399,7 @@ The number of floats for which space has been obtained from
the operating system, but that are not currently being used.
@item interval-size
Internal size of an interval object, i.e.@: @code{sizeof (struct interval)}.
Internal size of an interval object, i.e., @code{sizeof (struct interval)}.
@item used-intervals
The number of intervals in use.
......@@ -409,12 +409,12 @@ The number of intervals for which space has been obtained from
the operating system, but that are not currently being used.
@item buffer-size
Internal size of a buffer, i.e.@: @code{sizeof (struct buffer)}.
Internal size of a buffer, i.e., @code{sizeof (struct buffer)}.
(Do not confuse with the value returned by @code{buffer-size} function.)
@item used-buffers
The number of buffer objects in use. This includes killed buffers
invisible to users, i.e.@: all buffers in @code{all_buffers} list.
invisible to users, i.e., all buffers in @code{all_buffers} list.
@item unit-size
The unit of heap space measurement, always equal to 1024 bytes.
......@@ -699,7 +699,7 @@ in the file @file{lisp.h}.) If the primitive has no upper limit on
the number of Lisp arguments, it must have exactly two C arguments:
the first is the number of Lisp arguments, and the second is the
address of a block containing their values. These have types
@code{int} and @w{@code{Lisp_Object *}} respectively. Since
@code{int} and @w{@code{Lisp_Object *}} respectively. Since
@code{Lisp_Object} can hold any Lisp object of any data type, you
can determine the actual data type only at run time; so if you want
a primitive to accept only a certain type of argument, you must check
......@@ -900,11 +900,11 @@ following basic data types: integer, symbol, string, cons cell, float,
vectorlike or miscellaneous object. Each of these data types has the
corresponding tag value. All tags are enumerated by @code{enum Lisp_Type}
and placed into a 3-bit bitfield of the @code{Lisp_Object}. The rest of the
bits is the value itself. Integer values are immediate, i.e.@: directly
bits is the value itself. Integer values are immediate, i.e., directly
represented by those @dfn{value bits}, and all other objects are represented
by the C pointers to a corresponding object allocated from the heap. Width
of the @code{Lisp_Object} is platform- and configuration-dependent: usually
it's equal to the width of an underlying platform pointer (i.e.@: 32-bit on
it's equal to the width of an underlying platform pointer (i.e., 32-bit on
a 32-bit machine and 64-bit on a 64-bit one), but also there is a special
configuration where @code{Lisp_Object} is 64-bit but all pointers are 32-bit.
The latter trick was designed to overcome the limited range of values for
......
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