doc/*.tex: Minor source-level reformatting.

No effect on the document.

diff --git a/doc/clang.tex b/doc/clang.tex
index f5ccbb1913c9e8f3e2c5df31616beefe6221a04e..971981131afcc0658b1697799ef2c2adc6e7eb16 100644 (file)
--- a/doc/clang.tex
+++ b/doc/clang.tex
@@ -646,6 +646,7 @@ In Sod, the leaf types are
   interned) enumerated type with the given @<tag> and @<qualifier>s (all
   evaluated).
 \end{describe}
   interned) enumerated type with the given @<tag> and @<qualifier>s (all
   evaluated).
 \end{describe}

+

 \begin{describe}{fun}
     {make-enum-type @<tag> \&optional @<qualifiers> @> @<c-enum-type>}
   Return the (unique interned) C type object for the enumerated C type whose
 \begin{describe}{fun}
     {make-enum-type @<tag> \&optional @<qualifiers> @> @<c-enum-type>}
   Return the (unique interned) C type object for the enumerated C type whose


@@ -661,6 +662,7 @@ In Sod, the leaf types are
   interned) structured type with the given @<tag> and @<qualifier>s (all
   evaluated).
 \end{describe}
   interned) structured type with the given @<tag> and @<qualifier>s (all
   evaluated).
 \end{describe}

+

 \begin{describe}{fun}
     {make-struct-type @<tag> \&optional @<qualifiers> @> @<c-struct-type>}
   Return the (unique interned) C type object for the structured C type whose
 \begin{describe}{fun}
     {make-struct-type @<tag> \&optional @<qualifiers> @> @<c-struct-type>}
   Return the (unique interned) C type object for the structured C type whose


@@ -964,9 +966,9 @@ function type is the type of the function's return value.
 
   Keyword functions are never considered to be the same as ordinary
   functions.  Two keyword function types are considered to be the same if
 
   Keyword functions are never considered to be the same as ordinary
   functions.  Two keyword function types are considered to be the same if

-  their return types are the same, and their positional argument lists consist of
-  arguments with the same type, in the same order: the keyword arguments
-  accepted by the functions is not significant.
+  their return types are the same, and their positional argument lists
+  consist of arguments with the same type, in the same order: the keyword
+  arguments accepted by the functions is not significant.

 
   Keyword functions are constructed using an extended version of the @|fun|
   specifier used for ordinary C function types.  The extended syntax is as
 
   Keyword functions are constructed using an extended version of the @|fun|
   specifier used for ordinary C function types.  The extended syntax is as

diff --git a/doc/meta.tex b/doc/meta.tex
index 4b42a86f24e479f4b24b5fdf6e31b6dd8f07de7e..1ca5444b72d5d955bd5aba53f1b65ed336470f6a 100644 (file)
--- a/doc/meta.tex
+++ b/doc/meta.tex
@@ -151,11 +151,11 @@
 
 \begin{describe*}
     {\dhead{cls}{sod-initializer ()
 
 \begin{describe*}
     {\dhead{cls}{sod-initializer ()

-       \&key :slot :location :class :value}
+                  \&key :slot :location :class :value}

      \dhead{cls}{sod-instance-initializer (sod-initializer)
      \dhead{cls}{sod-instance-initializer (sod-initializer)

-       \&key :slot :location :class :value}
+                  \&key :slot :location :class :value}

      \dhead{cls}{sod-class-initializer (sod-initializer)
      \dhead{cls}{sod-class-initializer (sod-initializer)

-       \&key :slot :location :class :value}}
+                  \&key :slot :location :class :value}}

 \end{describe*}
 
 \begin{describe*}
 \end{describe*}
 
 \begin{describe*}

diff --git a/doc/parsing.tex b/doc/parsing.tex
index 17f0ecbdf5e6210834aa3f0e9e3b25bee7be4eff..cd0e12f4903f8be68682bebbb50b5470f8f82e47 100644 (file)
--- a/doc/parsing.tex
+++ b/doc/parsing.tex
@@ -252,6 +252,7 @@ Some scanners support an additional \emph{place-capture} protocol which
 allows rewinding the scanner to an earlier point in the input so that it can
 be scanned again.
 
 allows rewinding the scanner to an earlier point in the input so that it can
 be scanned again.
 

+

 \subsection{Basic scanner protocol} \label{sec:parsing.scanner.basic}
 
 The basic protocol supports stepping the scanner forward through its input
 \subsection{Basic scanner protocol} \label{sec:parsing.scanner.basic}
 
 The basic protocol supports stepping the scanner forward through its input


@@ -272,6 +273,7 @@ sequence, and detecting the end of the sequence.
   step the scanner.
 \end{describe}
 
   step the scanner.
 \end{describe}
 

+

 \subsection{Place-capture scanner protocol} \label{sec:parsing.scanner.place}
 
 The place-capture protocol allows rewinding to an earlier point in the
 \subsection{Place-capture scanner protocol} \label{sec:parsing.scanner.place}
 
 The place-capture protocol allows rewinding to an earlier point in the


@@ -319,6 +321,7 @@ the scanner and read that data again.  Therefore it's possible to
   return values are the values of the final @<form>.
 \end{describe}
 
   return values are the values of the final @<form>.
 \end{describe}
 

+

 \subsection{Scanner file-location protocol} \label{sec:parsing.scanner.floc}
 
 Some scanners participate in the file-location protocol
 \subsection{Scanner file-location protocol} \label{sec:parsing.scanner.floc}
 
 Some scanners participate in the file-location protocol


@@ -352,6 +355,7 @@ here.
   return nil.
 \end{describe*}
 
   return nil.
 \end{describe*}
 

+

 \subsection{Character scanners} \label{sec:parsing.scanner.char}
 
 Character scanners are scanners which read sequences of characters.
 \subsection{Character scanners} \label{sec:parsing.scanner.char}
 
 Character scanners are scanners which read sequences of characters.


@@ -412,6 +416,7 @@ operations to the sequence of characters held by a character scanner.
   character scanner protocols is suitable.  See @|make-scanner-stream|.
 \end{describe}
 
   character scanner protocols is suitable.  See @|make-scanner-stream|.
 \end{describe}
 

+

 \subsection{String scanners} \label{sec:parsing.scanner.string}
 
 A \emph{string scanner} is a simple kind of character scanner which reads
 \subsection{String scanners} \label{sec:parsing.scanner.string}
 
 A \emph{string scanner} is a simple kind of character scanner which reads


@@ -436,6 +441,7 @@ and place-capture protocols.
   to the end of the @<string>).
 \end{describe}
 
   to the end of the @<string>).
 \end{describe}
 

+

 \subsection{Character buffer scanners} \label{sec:parsing.scanner.charbuf}
 
 A \emph{character buffer scanner}, or \emph{charbuf scanner} for short, is an
 \subsection{Character buffer scanners} \label{sec:parsing.scanner.charbuf}
 
 A \emph{character buffer scanner}, or \emph{charbuf scanner} for short, is an


@@ -500,6 +506,7 @@ file-location protocols.
   at least once, or with $@<used> > @<start>$.
 \end{describe}
 
   at least once, or with $@<used> > @<start>$.
 \end{describe}
 

+

 \subsection{Token scanners} \label{sec:parsing.scanner.token}
 
 \begin{describe}{cls}
 \subsection{Token scanners} \label{sec:parsing.scanner.token}
 
 \begin{describe}{cls}


@@ -522,6 +529,7 @@ file-location protocols.
     {token-scanner-place-p @<value> @> @<generalized-boolean>}
 \end{describe}
 
     {token-scanner-place-p @<value> @> @<generalized-boolean>}
 \end{describe}
 

+

 \subsection{List scanners}
 
 \begin{describe}{ty}{list-scanner}
 \subsection{List scanners}
 
 \begin{describe}{ty}{list-scanner}