Date: Fri, 6 Dec 1996 16:01:20 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: archie@whistle.com (Archie Cobbs) Cc: terry@lambert.org, hackers@FreeBSD.ORG Subject: Re: Yacc -p<NAME> is broken Message-ID: <199612062301.QAA24585@phaeton.artisoft.com> In-Reply-To: <199612061955.LAA10393@bubba.whistle.com> from "Archie Cobbs" at Dec 6, 96 11:55:53 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > When you generate a y.tab.h file using yacc -p<NAME>... ie: > > > > yacc -v -p<NAME> > > > > In the file y.tab.h, you get: > > > > [.. etc ..] > > This is not meant to incite flamage, but ... why are you using > lex/yacc instead of flex/bison? FreeBSD lex *is* flex. So I *am* using flex (I have no choice, but I'd use it anyway because of "-i" simplifying command start tokens). The lex bugs are flex bugs. 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. Note: "use", as in "produce a non-free derivitive work from", not "utilize", as in "run the resulting binaries, but not give them away or sell them". The yacc bugs are yacc bugs, not bison bugs. If I were to utilize a tool other than yacc, it'd probably be SSL before it would be bison, anyway. 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?199612062301.QAA24585>