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

Jason Merrill <jason@cygnus.com>
7 May 1998 17:05:03 -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: Jason Merrill <jason@cygnus.com>
Newsgroups: comp.compilers
Date: 7 May 1998 17:05:03 -0400
Organization: Cygnus Solutions, Sunnyvale, CA
References: 98-05-022
Keywords: yacc, practice

>>>>> Tim Converse <converse@cs.uchicago.edu> writes:
> ... 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.


This used to be true, but is not now. From the Bison manual:


    As of Bison version 1.24, we have changed the distribution terms for
    yyparse to permit using Bison's output in non-free programs. Formerly,
    Bison parsers could be used only in programs that were free software.


Jason
--

Post a followup to this message

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