Update of /cvsroot/sbcl/sbcl/doc/manual
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8900/doc/manual
Modified Files:
debugger.texinfo
Log Message:
0.8.15:
some trivial text fixes (like s/the the/the/)
release, tagged as sbcl_0_8_15
Index: debugger.texinfo
===================================================================
RCS file: /cvsroot/sbcl/sbcl/doc/manual/debugger.texinfo,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- debugger.texinfo 14 Sep 2004 06:51:13 -0000 1.8
+++ debugger.texinfo 29 Sep 2004 19:34:40 -0000 1.9
@@ -790,7 +790,7 @@
If the heuristic doesn't work, the displayed source will be wrong, but will
probably be near the actual source. If the ``shape'' of the top-level form in
the source file is too different from the original form, then an error will be
-signaled. When the heuristic is used, the the source location commands are
+signaled. When the heuristic is used, the source location commands are
noticeably slowed.
Source location printing can also be confused if (after the source was
@@ -830,7 +830,7 @@
@item The block start location may be the same as the true location.
-@... The block start location will never be later in the the
+@item The block start location will never be later in the
program's flow of control than the true location.
@item No conditional control structures (such as @code{if},
@@ -1023,7 +1023,7 @@
@c @cindex Breakpoints
@c SBCL supports setting of breakpoints inside compiled functions and
-@... stepping of compiled code. Breakpoints can only be set at at known
+@c stepping of compiled code. Breakpoints can only be set at known
@c locations (@pxref{Unknown Locations and Interrupts}), so these
@c commands are largely useless unless the @code{debug} optimize quality
@c is at least @code{2} (@pxref{Debugger Policy Control}). These
|