From 4e65d3f7d1fddc478f2229494f333fd15646efb2 Mon Sep 17 00:00:00 2001 From: rtoy <rtoy> Date: Tue, 22 Jan 2008 21:52:21 +0000 Subject: [PATCH] Fix some overfull boxes by rewording a few items. --- docs/cmu-user/aliens.tex | 6 ++++-- docs/cmu-user/hierarchical-packages.tex | 12 ++++++------ docs/cmu-user/serve-event.tex | 2 +- 3 files changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/cmu-user/aliens.tex b/docs/cmu-user/aliens.tex index c0c29e0c3..db9f3e45b 100644 --- a/docs/cmu-user/aliens.tex +++ b/docs/cmu-user/aliens.tex @@ -966,8 +966,10 @@ possible using \code{malloc} or \code{make-alien} since we need about (n c-call:int :in)) (defun test-dotprod () - (let ((x (make-array 10000 :element-type 'double-float :initial-element 2d0)) - (y (make-array 10000 :element-type 'double-float :initial-element 10d0))) + (let ((x (make-array 10000 :element-type 'double-float + :initial-element 2d0)) + (y (make-array 10000 :element-type 'double-float + :initial-element 10d0))) (sys:without-gcing (let ((x-addr (sys:vector-sap x)) (y-addr (sys:vector-sap y))) diff --git a/docs/cmu-user/hierarchical-packages.tex b/docs/cmu-user/hierarchical-packages.tex index 22d2eb5ab..74e08a6be 100644 --- a/docs/cmu-user/hierarchical-packages.tex +++ b/docs/cmu-user/hierarchical-packages.tex @@ -56,7 +56,7 @@ modifications to the underlying \clisp{} implementation. Relative package names require only small and simple modifications. -\subsection{Relative package names} +\subsection{Relative Package Names} Relative package names are needed for the same reason as relative pathnames, for brevity and to reduce the brittleness of absolute @@ -65,7 +65,7 @@ dots. A single dot means the current package, two dots mean the parent of the current package, and so on. Table~\ref{tbl:hierarchical-packages} presents a number of examples, -assuming that packages named \verb|foo|, \verb|foo.bar|, +assuming that the packages named \verb|foo|, \verb|foo.bar|, \verb|mypack|, \verb|mypack.foo|, \verb|mypack.foo.bar|, \verb|mypack.foo.baz|, \verb|mypack.bar|, and \verb|mypack.bar.baz|, have all been created. @@ -113,7 +113,7 @@ Consider the following: When the current package (the value of the variable \code{*package*}) is \code{common-lisp-user}, you might expect \verb|.foo| to refer to -\verb|cl-user.foo|, but it does not. It refers to the non-existent +\verb|cl-user.foo|, but it does not. It actually refers to the non-existent package \verb|common-lisp-user.foo|. Note that the purpose of nicknames is to provide shorter names in place of the longer names that are designed to be fully descriptive. The hope is that @@ -172,7 +172,7 @@ proceeds as it does with a string argument.) Note that you should not use leading dots in package names when using hierarchical packages. -\subsubsection{Using hierarchical packages without modifying cl:find-package} +\subsubsection{Using Hierarchical Packages without Modifying cl:find-package} Even without the modifications to \code{cl:find-package}, authors need not avoid using relative package names, but the ability to reuse @@ -181,8 +181,8 @@ relative package names is restricted. Consider for example a module \verb|my.foo.baz| packages. In the code for each of the these packages there are relative package references, \verb|..bar| and \verb|..baz|. -Implementations that have the new \code{cl:find-package} would carry -the keyword \verb|:relative-package-names| on their \code{*features*} +Implementations that have the new \code{cl:find-package} would have +\verb|:relative-package-names| on their \code{*features*} list (this is the case of \cmucl{} releases starting from 18d). Then, in the \textit{foo} module, there would be definitions of the \verb|my.foo.bar| and \verb|my.foo.baz| packages like so: diff --git a/docs/cmu-user/serve-event.tex b/docs/cmu-user/serve-event.tex index e2e005ac5..bf4d8aa17 100644 --- a/docs/cmu-user/serve-event.tex +++ b/docs/cmu-user/serve-event.tex @@ -151,7 +151,7 @@ descriptor as it's single argument. This macro executes the supplied forms with a handler installed using \var{fd}, \var{direction}, and \var{function}. See - \code{system:add-fd-handler}. The forms are wrapped in an + \code{system:add-fd-handler}. The given forms are wrapped in an \code{unwind-protect}; the handler is removed (see \code{system:remove-fd-handler}) when done. \end{defmac} -- GitLab