305 |
@unnumbered Conditions for Using Bison |
@unnumbered Conditions for Using Bison |
306 |
|
|
307 |
As of Bison version 1.24, we have changed the distribution terms for |
As of Bison version 1.24, we have changed the distribution terms for |
308 |
@code{yyparse} to permit using Bison's output in nonfree programs. |
@code{yyparse} to permit using Bison's output in nonfree programs when |
309 |
Formerly, Bison parsers could be used only in programs that were free |
Bison is generating C code for LALR(1) parsers. Formerly, these |
310 |
software. |
parsers could be used only in programs that were free software. |
311 |
|
|
312 |
The other GNU programming tools, such as the GNU C compiler, have never |
The other GNU programming tools, such as the GNU C compiler, have never |
313 |
had such a requirement. They could always be used for nonfree |
had such a requirement. They could always be used for nonfree |
329 |
practical conditions for using Bison match the practical conditions for |
practical conditions for using Bison match the practical conditions for |
330 |
using the other GNU tools. |
using the other GNU tools. |
331 |
|
|
332 |
|
This exception applies only when Bison is generating C code for a |
333 |
|
LALR(1) parser; otherwise, the GPL terms operate as usual. You can |
334 |
|
tell whether the exception applies to your @samp{.c} output file by |
335 |
|
inspecting it to see whether it says ``As a special exception, when |
336 |
|
this file is copied by Bison into a Bison output file, you may use |
337 |
|
that output file without restriction.'' |
338 |
|
|
339 |
@include gpl.texi |
@include gpl.texi |
340 |
|
|
341 |
@node Concepts |
@node Concepts |