Xref: utzoo news.admin:2997 news.sysadmin:816 comp.sources.wanted:4532 comp.sources.d:2468 comp.unix.xenix:2662
Path: utzoo!attcan!uunet!husc6!mit-eddie!killer!chasm
From: chasm@killer.UUCP (Charles Marslett)
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: MKS yacc
Message-ID: <4775@killer.UUCP>
Date: 12 Jul 88 01:53:28 GMT
References: <3532@rpp386.UUCP> <135@dcs.UUCP> <235@pigs.UUCP> <4765@killer.UUCP>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 19

In article <4765@killer.UUCP>, richardh@killer.UUCP (Richard Hargrove) writes:
> It would seem that if AT&T were concerned about names and algorithms
> that they would have attempted to stop the MKS yacc distribution
> since a) the tool is named yacc, and b) it demonstrates a very high 
> degree of compatibility with Unix yacc (implying that the underlying
> algorithm(s) are the same).

Actually, I seem to recall that the MKS version of yacc is in fact a
licensed port of the real AT&T yacc -- I do not remember why or who led
me to this belief, is there any contradictory (or supporting) information
out there to clear up the confusion?  That would clear up why AT&T is not
after them!

> richard hargrove

Charles Marslett
chasm@killer.UUCP
> ...!{ihnp4 | codas | cbosgd}!killer!richardh
> --------------------------------------------