Date: Thu, 2 Feb 1995 16:37:49 -0800 (PST) From: Gordon Hogenson To: John Bodfish Cc: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Re: Flex and bison On Thu, 2 Feb 1995, John Bodfish wrote: > Previously, someone asked: > > > > Does 263 flex and/or bison generate C++ code. > > The following is an excerpt from the comp.compilers FAQ: language: BNF (yacc), Lex package: Bison++ and Flex++ version: 1.21-8 (bison), 2.3.8-7 (flex), 5 (flex++bison++misc) parts: translator, documentation, postscript, examples, DOS binary author: Alain Coetmeur location: cse.unl.edu in ~ftp/pub/nandy/c++/tools/LATEST/* Europe: mirrored on ftp.th-darmstadt.de description: A retargeting of bison-1 and flex 2.3 to C++, able to generate classes. As with Bison and Flex, these two tools are independent but designed for mutual compatibility. The version numbering has been changed for consistency with Flex and Bison, so versions of flex3.0.x and bison2.x of this package are are actually earlier versions, not later. Examples are provided to help in getting started. conformance: Mostly compatible with flex2.3 and bison 1 in C, apart from the ability to generate classes. features: Almost all symbol names can be redefined, parsers can be shared in C and C++ in the same headers... very extensible... flex++ support IOSTREAM and STDIO in C++. bugs: Contact coetmeur AT icdc DOT fr (current author and maintainer). restriction: GNU License for bison++. Same as flex for flex++. ports: SUNOS4, DOS, and same ports as Flex/Bison, Windows NT (tested) portability: Larger memory model required on DOS (DOS binary supplied). status: active, supported, might not support flex 2.4 discussion: coetmeur AT icdc DOT fr, news: comp.compiler, or comp.lang.c++ help: coetmeur AT icdc DOT fr, news: comp.compiler, or comp.lang.c++ for substantial problems. support: see help, no commercial support. (volunteer ?) announcements: mail list locally maintained by coetmeur AT icdc DOT fr, news: comp.compiler comp.lang.c++ updated: 1994/02/07 lref: C lref: C++ lref: Lex lref: yacc ------------------------------------------------------------------------- Perhaps this is what the original poster was seeking. Gordon.