Xref: utzoo comp.lang.c:26139 comp.misc:8248
Path: utzoo!attcan!uunet!ogicse!uwm.edu!rpi!zaphod.mps.ohio-state.edu!think!snorkelwacker!spdcc!esegue!johnl
From: johnl@esegue.segue.boston.ma.us (John R. Levine)
Newsgroups: comp.lang.c,comp.misc
Subject: Re: Legal uses of lex & yacc
Message-ID: <1990Feb21.160821.2506@esegue.segue.boston.ma.us>
Date: 21 Feb 90 16:08:21 GMT
References: <90049.104719MCCABE@MTUS5.BITNET> <271@xyzzy.UUCP>
Reply-To: johnl@esegue.segue.boston.ma.us (John R. Levine)
Organization: Segue Software, Cambridge MA
Lines: 18

In article <271@xyzzy.UUCP> kan@tom.dg.com () writes:
>But if you intend to distribute only C code, i.e. after you've run
>your work through the "Official" Lex and Yacc, you can be prosecuted
>for copyright infringement!  ...

I wish people would check their "facts."  AT&T has for several years
explicitly permitted programs built with lex and yacc to be redistributed
without restriction.  The same goes for executables built with the C library.

For those who don't like yacc and lex, Bob Corbett's Berkeley Yacc is
entirely public domain.  Vern Paxton's flex is subject to the Berkeley
copyright (which allows unlimited redistribution so long as you include
Berkeley's copyright and disclaimer.)  The flex parser skeleton is public
domain.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@esegue.segue.boston.ma.us, {ima|lotus|spdcc}!esegue!johnl
"Now, we are all jelly doughnuts."