Added environment for defining PyVM instructions. This is only used in
the libdis.tex file I'm about to check in. I'm not sure this is really an optimal solution yet, but it may be the best alternative. It avoids describing the instructions as either data items or functions. This change was discussed with Guido. (Guido: Take a look at the LaTeX output for this; if this is reasonable I'll go ahead and update the perl code in myformat.perl to match.)
This commit is contained in:
parent
b7f1afe4a8
commit
a610f9f8c1
|
@ -161,6 +161,12 @@
|
|||
\let\enddatadesc\endfulllineitems
|
||||
|
||||
|
||||
% opcodedesc should be called as an \begin{opcodedesc} ... \end{opcodedesc}
|
||||
\newcommand{\opcodeline}[2]{\item[\code{#1\quad\varvars{#2}}]\ttindex{#1}}
|
||||
\newcommand{\opcodedesc}[2]{\fulllineitems\opcodeline{#1}{#2}}
|
||||
\let\endopcodedesc\endfulllineitems
|
||||
|
||||
|
||||
% Define \dataitem{name}: define a data item
|
||||
\newcommand{\dataitem}[1]{%
|
||||
\ttindex{#1}%
|
||||
|
|
Loading…
Reference in New Issue