|Parsing C++ with lex++ and bison++ ? email@example.com (1994-06-16)|
|Re: Parsing C++ with lex++ and bison++ ? firstname.lastname@example.org (1994-06-19)|
|Re: Parsing C++ with lex++ and bison++ ? email@example.com (Boris Burshteyn) (1994-06-23)|
|Re: Parsing C++ with lex++ and bison++ ? firstname.lastname@example.org (1994-06-25)|
|Re: Parsing C++ with lex++ and bison++ ? email@example.com (Boris Burshteyn) (1994-06-29)|
|From:||firstname.lastname@example.org (Jan-Peter de Ruiter)|
|Keywords:||C++, parse, tools|
|Date:||Sun, 19 Jun 1994 13:56:06 GMT|
: Has any anyone used lex++ and bison++ to parse C++ code, successfully.
: Are there any bugs in it. The bottom line is, is it worth using it at
About the grammar you need for C++, I know nothing. But with regard to
using lex++ and bison++, I have a comment that you might appreciate.
Flex++ and Bison++ do generate C++ code, but they do not cooperate well
with some C++ features. A great disappointment for me was that I couldn't
use $-types that were classes with user-defined constructors. You have to
do everything with pointers, i.e. do your own memory management. This, for
me, spoiled all the fun.
Return to the
Search the comp.compilers archives again.