Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site orca.UUCP
Path: utzoo!linus!decvax!tektronix!orca!andrew
From: andrew@orca.UUCP (Andrew Klossner)
Newsgroups: net.unix-wizards
Subject: Re: yacc: public domain?
Message-ID: <1276@orca.UUCP>
Date: Sat, 29-Dec-84 21:28:26 EST
Article-I.D.: orca.1276
Posted: Sat Dec 29 21:28:26 1984
Date-Received: Tue, 1-Jan-85 05:50:39 EST
References: <6779@brl-tgr.ARPA> <2114@umcp-cs.UUCP>
Organization: Tektronix, Wilsonville OR
Lines: 22

[]

	"I have heard the claim (and it makes sense to me) that SOURCE
	code put out by yacc is proprietary, since it contains
	/usr/lib/yaccpar.  I've never heard it claimed (but wouldn't be
	TOO surprised at ANYTHING AT&T does) that object code produced
	with the aid of yacc is proprietary."

In 1982, it was the official legal position of AT&T that object code
from yacc is proprietary.

I checked into this because the company I was working for was
considering OEM'ing the Aztec C package for CP/M-80.  The problem is
that the included assembler (but not the compiler) was written using
yacc.  We concluded that Manx was violating a Unix license, and decided
to steer clear.

You can make your yacc output be non-proprietary by rewriting
/usr/lib/yaccpar.

  -- Andrew Klossner   (decvax!tektronix!orca!andrew)       [UUCP]
                       (orca!andrew.tektronix@csnet-relay)  [ARPA]