From: Fred Drake <fdrake@acm.org>
Date: Thu, 31 Aug 2000 16:26:35 +0000 (+0000)
Subject: UNARY_NEG is supposed to be UNARY_NEGATIVE (spotted by Charles Waldman
X-Git-Tag: v2.0b1~131
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4c3f797128bdd6139390d0b3180bda41adca5db1;p=python

UNARY_NEG is supposed to be UNARY_NEGATIVE (spotted by Charles Waldman
<cgw@fnal.gov>).

Fix minor problem with EXTENDED_ARG description markup..
---

diff --git a/Doc/lib/libdis.tex b/Doc/lib/libdis.tex
index 593daca19e..9d709ac484 100644
--- a/Doc/lib/libdis.tex
+++ b/Doc/lib/libdis.tex
@@ -146,7 +146,7 @@ push the result back on the stack.
 Implements \code{TOS = +TOS}.
 \end{opcodedesc}
 
-\begin{opcodedesc}{UNARY_NEG}{}
+\begin{opcodedesc}{UNARY_NEGATIVE}{}
 Implements \code{TOS = -TOS}.
 \end{opcodedesc}
 
@@ -595,7 +595,7 @@ information.
 Prefixes any opcode which has an argument too big to fit into the
 default two bytes.  \var{ext} holds two additional bytes which, taken
 together with the subsequent opcode's argument, comprise a four-byte
-argument, \var {ext} being the two most-significant bytes.
+argument, \var{ext} being the two most-significant bytes.
 \end{opcodedesc}
 
 \begin{opcodedesc}{CALL_FUNCTION_VAR}{argc}