diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2002-09-07 06:33:29 +0000 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2002-09-07 06:33:29 +0000 |
| commit | 262aa8dd5934143c2403150c98fce44c32747930 (patch) | |
| tree | 49986f62b3694fe814d89415185951ffed1306f2 | |
| parent | 0252b55c07fc9d4b69e668fd2f0204bbe92295a1 (diff) | |
| download | bison-262aa8dd5934143c2403150c98fce44c32747930.tar.gz | |
(Conditions): Say that the exceptions apply only to C LALR(1) parsers.
| -rw-r--r-- | doc/bison.texinfo | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/bison.texinfo b/doc/bison.texinfo index 066213a6..16b8685a 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -305,9 +305,9 @@ This edition corresponds to version @value{VERSION} of Bison. @unnumbered Conditions for Using Bison As of Bison version 1.24, we have changed the distribution terms for -@code{yyparse} to permit using Bison's output in nonfree programs. -Formerly, Bison parsers could be used only in programs that were free -software. +@code{yyparse} to permit using Bison's output in nonfree programs when +Bison is generating C code for LALR(1) parsers. Formerly, these +parsers could be used only in programs that were free software. The other GNU programming tools, such as the GNU C compiler, have never had such a requirement. They could always be used for nonfree @@ -329,6 +329,13 @@ encourage people to make other software free. So we decided to make the practical conditions for using Bison match the practical conditions for using the other GNU tools. +This exception applies only when Bison is generating C code for a +LALR(1) parser; otherwise, the GPL terms operate as usual. You can +tell whether the exception applies to your @samp{.c} output file by +inspecting it to see whether it says ``As a special exception, when +this file is copied by Bison into a Bison output file, you may use +that output file without restriction.'' + @include gpl.texi @node Concepts |