Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site celerity.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!hao!hplabs!sdcrdcf!sdcsvax!bmcg!sdcc6!celerity!ron
From: ron@celerity.UUCP (Ron McDaniels)
Newsgroups: net.unix-wizards,net.legal
Subject: Re: yacc: public domain?
Message-ID: <260@celerity.UUCP>
Date: Thu, 31-Jan-85 13:13:27 EST
Article-I.D.: celerity.260
Posted: Thu Jan 31 13:13:27 1985
Date-Received: Mon, 4-Feb-85 03:39:54 EST
References: <315@desint.UUCP> <45@mit-athena.ARPA> <305@terak.UUCP>
Reply-To: ron@celerity.UUCP ( McDaniels)
Organization: Celerity Computing, San Diego, Ca.
Lines: 20
Xref: watmath net.unix-wizards:11869 net.legal:1376
Summary: 

In article <305@terak.UUCP> doug@terak.UUCP (Doug Pardee) writes:
>> How do I
>> know that the output of the C compiler isn't the legal property of
>> the compiler's author?
>
>In the case if C (and most other high-level languages), the output
>of the compiler isn't usually considered to be property of the
>compiler company. . . . . .

Scratch "usually". If I buy a meat grinder from you and put my steak through
it to make hamburger (assume a low quality cut :-), the hamburger doesn't become
yours just because you manufactured the meat grinder. If I make a sandwich from
the hamburger with your bread and mayo, then the sandwich isn't completely mine.

Well, it makes sense to me!! :-)


Ron McDaniels
CELERITY COMPUTING
{decvax || ucbvax || ihnp4 || akgua || philabs}!sdcsvax!celerity!ron