Xref: utzoo news.admin:3010 news.sysadmin:838 comp.sources.wanted:4585 comp.sources.d:2500 comp.unix.xenix:2692
Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ames!oliveb!epimass!jbuck
From: jbuck@epimass.EPI.COM (Joe Buck)
Newsgroups: news.admin,news.sysadmin,comp.sources.wanted,comp.sources.d,comp.unix.xenix
Subject: Re: Please remove PD-YACC sources from your machine IMMEDIATELY
Summary: We were talking about the DECUS YACC, not MKS YACC.
Message-ID: <2307@epimass.EPI.COM>
Date: 17 Jul 88 20:31:18 GMT
References: <3532@rpp386.UUCP> <135@dcs.UUCP> <235@pigs.UUCP> <4765@killer.UUCP> <4775@killer.UUCP> <99@obie.UUCP> <142@dcs.UUCP>
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 21

In article <142@dcs.UUCP> wnp@dcs.UUCP (Wolf N. Paul) writes:
>In article <99@obie.UUCP> wes@obie.UUCP (Barnacle Wes) writes:
>>Yes, most of the tools MKS produces are (debugged, well-ported) licensed
>>versions of gin-yoo-ine AT&T products.
>According to a posting by Alex White of MKS a few weeks ago, the MKS Toolkit
>does not contain any AT&T source code; ...

Interesting, but not relevant to the original flame war.  The version
of yacc that was yanked came off of a DECUS tape at some point; that
version of yacc is well-known to be a ripoff created by editing the
original AT&T source and DECUS no longer distributes it.

If MKS has a PD-yacc, that's wonderful.  So does the GNU project
(Bison).  As far as I know, AT&T has never claimed any rights over
all LR parser generators or even the name "yacc" -- just the right
to their own source code.
-- 
- Joe Buck  {uunet,ucbvax,pyramid,<smart-site>}!epimass.epi.com!jbuck
jbuck@epimass.epi.com	Old Arpa mailers: jbuck%epimass.epi.com@uunet.uu.net
	If you leave your fate in the hands of the gods, don't be 
	surprised if they have a few grins at your expense.	- Tom Robbins