bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: doc: mfcalc: demonstrate %printer


From: Akim Demaille
Subject: Re: doc: mfcalc: demonstrate %printer
Date: Mon, 19 Mar 2012 11:21:28 +0100

Le 17 mars 2012 à 00:50, Tim Landscheidt a écrit :

Thanks a lot for the proof reading!

On second thought, I think I will move this material in
the "Understanding" chapter, where %verbose is discussed.
So this is not ready for inclusion.

>> +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
>> address@hidden 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)
>               ^^^^^^^^^^^
>> address@hidden directive.
>> [...]
> 
> I don't quite get the meaning of this; what's "that parser"
> in this context?

Words were missing ;)

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 a description of that parser; this is the purpose of (admittedly
ill-named) @code{%verbose} directive.


>> [...]
>> +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".

OK, I changed this in my copy.  Thanks!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]