Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Dec 1996 17:48:25 -0700 (MST)
From:      Terry Lambert <terry@lambert.org>
To:        chuckr@glue.umd.edu (Chuck Robey)
Cc:        terry@lambert.org, archie@whistle.com, hackers@FreeBSD.ORG
Subject:   Re: Yacc -p<NAME> is broken
Message-ID:  <199612070048.RAA24781@phaeton.artisoft.com>
In-Reply-To: <Pine.OSF.3.95.961206190548.16014C-100000@carrier.eng.umd.edu> from "Chuck Robey" at Dec 6, 96 07:09:56 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> > I'm using yacc instead of bison because of the GPL.  The yacc/bison
> > grammar->code reduction includes code distributed with the tool.  For
> > bison, this code is GPL'ed.  For yacc, it is not.  I don't want the
> > resulting code to be GPL restricted about how I can use it, therefore
> > I use yacc.
> 
> Terry, I will be the first to admit I'm no lawyer, but I thought that the
> output from bison was not in itself GPL'ed, just the bison code itself.
> Let me quote the part I think is relevant from the COPYING file from bison
> 1.25:

See Nate's reply.  The rote code coming out for the y.tab.c equivalent
used to have a GNU "Copyleft" notice in it.  This is because the code
produced is not entirely output; it also includes static information
stuffed in there by bison itself.  The static information was what
was in question.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612070048.RAA24781>