creating non-GPL'ed C++ parser code -- flex++ and yacc?

Tim Converse <converse@cs.uchicago.edu>
4 May 1998 23:08:15 -0400

          From comp.compilers
Related articles
creating non-GPL'ed C++ parser code -- flex++ and yacc? converse@cs.uchicago.edu (Tim Converse) (1998-05-04)
Re: creating non-GPL'ed C++ parser code -- flex++ and yacc? burley@cygnus.com (Craig Burley) (1998-05-07)
Re: creating non-GPL'ed C++ parser code -- flex++ and yacc? jason@cygnus.com (Jason Merrill) (1998-05-07)
Re: creating non-GPL'ed C++ parser code -- flex++ and yacc? corbett@lupa.Eng.Sun.COM (1998-05-12)
Re: creating non-GPL'ed C++ parser code -- flex++ and yacc? tkb@access.mountain.net (1998-05-15)
| List of all articles for this month |
From: Tim Converse <converse@cs.uchicago.edu>
Newsgroups: comp.compilers
Date: 4 May 1998 23:08:15 -0400
Organization: Univ. of Chicago, Computer Science
Keywords: lex, yacc, question, C++

I'm new to lex and yacc-like tools, but am interested in using them to
produce C++ code. The project I'm working on is for a commercial
shop, so the code that is produced cannot be copylefted. As I
understand it, lexers produced with flex(++) can be freely used, but
parsers created with bison(++) are covered under the GNU GPL. For
this project, this rules out bison.


Does anyone know if yacc can generate C++ code? If not, does anyone
have any suggestions about how to produce non-GPL'ed parser code in
C++? (Any suggestions, that is, other than the obvious one: writing
it myself. :)


thanks,
Tim Converse




--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.