* doc/bison.texinfo (How Can I Reset the Parser): More about start

conditions.
From Bruno Haible.
This commit is contained in:
Akim Demaille
2003-12-02 17:08:31 +00:00
parent 26e06a2157
commit b165c324a3
3 changed files with 12 additions and 0 deletions

View File

@@ -1,3 +1,9 @@
2003-12-02 Akim Demaille <akim@epita.fr>
* doc/bison.texinfo (How Can I Reset the Parser): More about start
conditions.
From Bruno Haible.
2003-11-18 Alexandre Duret-Lutz <adl@gnu.org>
* doc/bison.texinfo (Bison Options): Escape `@' in `$@'.

1
THANKS
View File

@@ -12,6 +12,7 @@ Art Haas ahaas@neosoft.com
Benoit Perrot benoit.perrot@epita.fr
Bert Deknuydt Bert.Deknuydt@esat.kuleuven.ac.be
Bruce Lilly blilly@erols.com
Bruno Haible bruno@clisp.org
Charles-Henri de Boysson de-boy_c@epita.fr
Cris Bailiff c.bailiff+bison@awayweb.com
Cris van Pelt cris@amf03054.office.wxs.nl

View File

@@ -6508,6 +6508,11 @@ handle features like include files, you might consider using Flex
functions like @samp{yy_switch_to_buffer} that manipulate multiple
input buffers.
If your Flex-generated scanner uses start conditions (@pxref{Start
conditions, , Start conditions, flex, The Flex Manual}), you might
also want to reset the scanner's state, i.e., go back to the initial
start condition, through a call to @samp{BEGIN (0)}.
@node Strings are Destroyed
@section Strings are Destroyed