Akim Demaille <[email protected]> wrote:
> [...]
> +In addition, in order to support run-time traces, the prologue is extend
^^^^^^
> +with:
> [...]
This should probably read "extended" as well :-).
> [...]
> +The @code{%define} directive will instruct Bison to generate run-time trace
> +support. Then, activation of these traces is controlled at run-time by the
> +@code{yydebug} variable, which is disabled by default. Because these traces
> +will refer to the ``states'' of the parser, it is helpful to ask for the
> +creation of that parser; this is the purpose of (admittedly ill-named)
^^^^^^^^^^^
> +@code{%verbose} directive.
> [...]
I don't quite get the meaning of this; what's "that parser"
in this context?
> [...]
> +Anticipating the completion of the sources of this example, here is a sample
> +of the information provided by run-time traces. The function @code{main} is
> +modified so that option @option{-p} activates the generated tracing code.
> +The traces are sent onto the standard error.
^^^^^^^^^^^^^^^^^^
> [...]
I believe "standard error" is used without "the".
Tim
