(libparser.tex): Added note that the line number for a terminal token
indicates the line on which the token ends rather than starts (a side effect of interpreting the parse tree nodes directly). Maybe I'll fix this for Python 2.0.
This commit is contained in:
parent
ba469ba9d7
commit
9abe64a395
|
@ -166,8 +166,9 @@ tuple representation and converting that to nested lists.
|
|||
|
||||
If \code{\var{line_info}} is true, line number information will be
|
||||
included for all terminal tokens as a third element of the list
|
||||
representing the token. This information is omitted if the flag is
|
||||
false or omitted.
|
||||
representing the token. Note that the line number provided specifies
|
||||
the line on which the token \emph{ends\/}. This information is
|
||||
omitted if the flag is false or omitted.
|
||||
\end{funcdesc}
|
||||
|
||||
\begin{funcdesc}{ast2tuple}{ast\optional{\, line_info\code{ = 0}}}
|
||||
|
|
|
@ -166,8 +166,9 @@ tuple representation and converting that to nested lists.
|
|||
|
||||
If \code{\var{line_info}} is true, line number information will be
|
||||
included for all terminal tokens as a third element of the list
|
||||
representing the token. This information is omitted if the flag is
|
||||
false or omitted.
|
||||
representing the token. Note that the line number provided specifies
|
||||
the line on which the token \emph{ends\/}. This information is
|
||||
omitted if the flag is false or omitted.
|
||||
\end{funcdesc}
|
||||
|
||||
\begin{funcdesc}{ast2tuple}{ast\optional{\, line_info\code{ = 0}}}
|
||||
|
|
Loading…
Reference in New Issue