summaryrefslogtreecommitdiffstats
path: root/Doc/lib/libdis.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1997-12-04 04:57:56 (GMT)
committerFred Drake <fdrake@acm.org>1997-12-04 04:57:56 (GMT)
commit1cf87496a641168969e3a95ba2cf04c922b36e34 (patch)
tree0ea3126dfe8c57ddc6a9e8008e8433a63dca30d5 /Doc/lib/libdis.tex
parent7381e28399ea31b26dfa1f0e1db1a85bd4bf37c3 (diff)
downloadcpython-1cf87496a641168969e3a95ba2cf04c922b36e34.zip
cpython-1cf87496a641168969e3a95ba2cf04c922b36e34.tar.gz
cpython-1cf87496a641168969e3a95ba2cf04c922b36e34.tar.bz2
Arg; more nits, but I may as well finish the job.
Removed the large comment remaining from the template documentation section; the template tells us to remove these once they're not needed. Remove some trailing whitespace from VM instruction pseudo-code.
Diffstat (limited to 'Doc/lib/libdis.tex')
-rw-r--r--Doc/lib/libdis.tex26
1 files changed, 6 insertions, 20 deletions
diff --git a/Doc/lib/libdis.tex b/Doc/lib/libdis.tex
index 30d966d..018fd1b 100644
--- a/Doc/lib/libdis.tex
+++ b/Doc/lib/libdis.tex
@@ -35,20 +35,6 @@ The \code{dis} module defines the following functions:
\renewcommand{\indexsubitem}{(in module dis)}
-% ---- 3.2. ----
-% For each function, use a ``funcdesc'' block. This has exactly two
-% parameters (each parameters is contained in a set of curly braces):
-% the first parameter is the function name (this automatically
-% generates an index entry); the second parameter is the function's
-% argument list. If there are no arguments, use an empty pair of
-% curly braces. If there is more than one argument, separate the
-% arguments with backslash-comma. Optional parts of the parameter
-% list are contained in \optional{...} (this generates a set of square
-% brackets around its parameter). Arguments are automatically set in
-% italics in the parameter list. Each argument should be mentioned at
-% least once in the description; each usage (even inside \code{...})
-% should be enclosed in \var{...}.
-
\begin{funcdesc}{dis}{\optional{bytesource}}
Disassemble the \var{bytesource} object. \var{bytesource} can denote
either a class, a method, a function, or a code object. For a class,
@@ -196,27 +182,27 @@ Implements \code{TOS = TOS1 - TOS}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_SUBSCR}{}
-Implements \code{TOS = TOS1[TOS] }.
+Implements \code{TOS = TOS1[TOS]}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_LSHIFT}{}
-Implements \code{TOS = TOS1 << TOS }.
+Implements \code{TOS = TOS1 << TOS}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_RSHIFT}{}
-Implements \code{TOS = TOS1 >> TOS }.
+Implements \code{TOS = TOS1 >> TOS}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_AND}{}
-Implements \code{TOS = TOS1 and TOS }.
+Implements \code{TOS = TOS1 and TOS}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_XOR}{}
-Implements \code{TOS = TOS1 \^{ }TOS }.
+Implements \code{TOS = TOS1 \^{ }TOS}.
\end{opcodedesc}
\begin{opcodedesc}{BINARY_OR}{}
-Implements \code{TOS = TOS1 or TOS }.
+Implements \code{TOS = TOS1 or TOS}.
\end{opcodedesc}
The slice opcodes take up to three parameters.