Related articles |
---|
lex and yacc for C++ ubacw00@ucl.ac.uk (1992-06-16) |
Re: lex and yacc for C++ vern@daffy.ee.lbl.gov (1992-06-17) |
Re: lex and yacc for C++ dkoosis@aristotle.sbi.com (1992-06-17) |
Re: lex and yacc for C++ ipser@solomon.technet.sg (1992-06-18) |
Re: lex and yacc for C++ ken@syd.dit.csiro.au (1992-06-18) |
Re: lex and yacc for C++ collison@osf.org (1992-06-18) |
Newsgroups: | comp.compilers |
From: | collison@osf.org |
Keywords: | yacc, GCC, C++ |
Organization: | Open Software Foundation |
References: | 92-06-080 |
Date: | Thu, 18 Jun 1992 13:09:55 GMT |
In article 92-06-080, ken@syd.dit.csiro.au (Ken Yap) writes:
|> |[The distributed versions of flex and bison handle only C.
|>
|> Not so. I'm compiling bison generated code with g++ and cfront. It's
|> properly prototyped. But it isn't C++ in the OOpy sense. Don't know about
|> flex.
There is a version of bison that generates c++ classes also.
Archie says:
Host wilbur.stanford.edu
Location: /pub
FILE -rw-r--r-- 101423 Aug 7 1991 bison++-1.04.tar.Z
--Mike
------------------------
Michael Collison
Open Software Foundation
11 Cambride Center
Cambridge, Ma 02142
email: collison@osf.org
[I picked it up and looked at it; it makes the parser into a class so you can
have multiple instances of a parser and limit symbol collisions. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.