Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-athena.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!whuxlm!akgua!mcnc!decvax!mit-athena!jc
From: jc@mit-athena.ARPA (John Chambers)
Newsgroups: net.unix-wizards,net.legal
Subject: Re: yacc: public domain? (flame on)
Message-ID: <45@mit-athena.ARPA>
Date: Thu, 24-Jan-85 10:18:08 EST
Article-I.D.: mit-athe.45
Posted: Thu Jan 24 10:18:08 1985
Date-Received: Mon, 28-Jan-85 05:07:35 EST
References: <315@desint.UUCP>
Organization: MIT, Project Athena, Cambridge, Ma.
Lines: 19
Xref: watmath net.unix-wizards:11737 net.legal:1357

Hey, haven't we sorta lost track of the original question here?  As 
I understand it, there is a suggestion that code produced by yacc
belongs to AT&T or Bell Labs or somebody like that.  Exactly which 
corporate entity is named isn't the important question.  The important
question is: If I write a program using yacc (or lex), and it turns
out to be a best-seller, can AT&T or some other corporate clone come
along and claim all my royalties for their own coffers?

Until this is settled, I don't think I'll use yacc or lex.  In fact,
maybe I shouldn't even be using any high-level language.  How do I
know that the output of the C compiler isn't the legal property of
the compiler's author?

Hey, anyone out there know the real legal situation?  This is not a
frivolous question.  We're talking about us little guys having to
give up all rights to our creation because we happened to use some
corporation's tool to produce it.

				John Chambers