From 92e590b029e3cffc62b2876149ab257f0e6d8eb3 Mon Sep 17 00:00:00 2001 From: Mark Wooding Date: Thu, 8 Aug 2019 01:17:15 +0100 Subject: [PATCH] doc/concepts.tex, doc/syntax.tex: Replace `\textsf{...}' by `@|...|'. Also, replace an enterprising combination of the `quote' environment with `\textsf' by `prog'. These were all very old. --- doc/concepts.tex | 2 +- doc/syntax.tex | 27 +++++++++++++-------------- 2 files changed, 14 insertions(+), 15 deletions(-) diff --git a/doc/concepts.tex b/doc/concepts.tex index 970b710..b8dcacf 100644 --- a/doc/concepts.tex +++ b/doc/concepts.tex @@ -695,7 +695,7 @@ entry functions. node [above right = 0mm and -8mm] {$\vcenter{\hbox{\Huge\textcolor{red}{!}}} \vcenter{\hbox{\begin{tabular}[c]{l} - \textsf{next_method} \\ + @|next_method| \\ pointer is null \end{tabular}}}$}; diff --git a/doc/syntax.tex b/doc/syntax.tex index 22fb1d8..75aa36e 100644 --- a/doc/syntax.tex +++ b/doc/syntax.tex @@ -63,8 +63,8 @@ could be a token. \end{grammar} The precise definition of @ is left to the function -\textsf{alpha-char-p} in the hosting Lisp system. For portability, -programmers are encouraged to limit themselves to the standard ASCII letters. +@|alpha-char-p| in the hosting Lisp system. For portability, programmers are +encouraged to limit themselves to the standard ASCII letters. There are no reserved words at the lexical level, but the higher-level syntax recognizes certain identifiers as \emph{keywords} in some contexts. There is @@ -550,9 +550,9 @@ A search is made for a module source file as follows. \begin{itemize} \item The module name @ is converted into a filename by appending @`.sod', if it has no extension already.\footnote{% - Technically, what happens is \textsf{(merge-pathnames name (make-pathname - :type "SOD" :case :common))}, so exactly what this means varies - according to the host system.} % + Technically, what happens is @|(merge-pathnames name (make-pathname :type + "SOD" :case :common))|, so exactly what this means varies according to + the host system.} % \item The file is looked for relative to the directory containing the importing module. \item If that fails, then the file is looked for in each directory on the @@ -562,7 +562,7 @@ A search is made for a module source file as follows. \end{itemize} At this point, if the file has previously been imported, nothing further happens.\footnote{% - This check is done using \textsf{truename}, so it should see through simple + This check is done using @|truename|, so it should see through simple tricks like symbolic links. However, it may be confused by fancy things like bind mounts and so on.} % @@ -579,23 +579,22 @@ A search is made for a Lisp source file as follows. \begin{itemize} \item The name @ is converted into a filename by appending @`.lisp', if it has no extension already.\footnote{% - Technically, what happens is \textsf{(merge-pathnames name (make-pathname - :type "LISP" :case :common))}, so exactly what this means varies - according to the host system.} % + Technically, what happens is @|(merge-pathnames name (make-pathname :type + "LISP" :case :common))|, so exactly what this means varies according to + the host system.} % \item A search is then made in the same manner as for module imports (\xref{sec:syntax-module}). \end{itemize} -If the file is found, it is loaded using the host Lisp's \textsf{load} -function. +If the file is found, it is loaded using the host Lisp's @|load| function. Note that Sod doesn't attempt to compile Lisp files, or even to look for existing compiled files. The right way to package a substantial extension to the Sod translator is to provide the extension as a standard ASDF system (or similar) and leave a dropping @|foo-extension.lisp| in the module path saying something like -\begin{quote} - \textsf{(asdf:load-system :foo-extension)} -\end{quote} +\begin{prog} + (asdf:load-system :foo-extension) +\end{prog} which will arrange for the extension to be compiled if necessary. (This approach means that the language doesn't need to depend on any -- 2.11.0