[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison/flex compatibility revisited
From: |
John |
Subject: |
Re: Bison/flex compatibility revisited |
Date: |
Wed, 26 Feb 2003 18:26:52 -0500 (EST) |
> > Any code that explicitly references YY_G is broken. YY_G is an
> > internal macro, and subject to change.
>
> But with a reentrant lexical analyzer, yyout is defined as
> #define yyout YY_G(yyout_r)
> which obviously isn't going to work if there's no definition
> of YY_G and/or nothing in which yyout_r is a member.
> Any code using yyout therefore needs YY_G;
That's what the function yyget_out() is for. See the section titled,
"Functions and Macros Available in Reentrant C Scanners", in the flex
manual.
- Bison/flex compatibility revisited, Bruce Lilly, 2003/02/24
- Re: Bison/flex compatibility revisited, Paul Eggert, 2003/02/25
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/25
- Re: Bison/flex compatibility revisited, Paul Eggert, 2003/02/25
- Re: Bison/flex compatibility revisited, John, 2003/02/25
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited,
John <=
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26
- Re: Bison/flex compatibility revisited, Paul Eggert, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26
- Re: Bison/flex compatibility revisited, Bruce Lilly, 2003/02/26
- Re: Bison/flex compatibility revisited, John, 2003/02/26