Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watdaisy.UUCP
Path: utzoo!watmath!watdaisy!ndiamond
From: ndiamond@watdaisy.UUCP (Norman Diamond)
Newsgroups: net.unix-wizards,net.legal
Subject: Re: yacc: public domain?
Message-ID: <6899@watdaisy.UUCP>
Date: Wed, 30-Jan-85 13:47:16 EST
Article-I.D.: watdaisy.6899
Posted: Wed Jan 30 13:47:16 1985
Date-Received: Thu, 31-Jan-85 00:33:04 EST
References: <315@desint.UUCP> <45@mit-athena.ARPA> <305@terak.UUCP>
Organization: U of Waterloo, Ontario
Lines: 30
Xref: watmath net.unix-wizards:11782 net.legal:1370

> 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.  After all, they would be hard-pressed to show
> that your object code duplicates, or is a translation of, their
> compiler.  On the contrary, you can show relatively easily that
> it is a translation of YOUR source program.
> 
> BUT!!!!  High-level languages almost always have an object-time
> library associated with them, and direct copies of subroutines
> from this library ARE linked in to your object deck.  Almost all
> compilers come with a prohibition against commercial sales of
> programs which were linked with their object libraries!
> 
> Copyright infringement on compilers' subroutine libraries IS taken
> seriously.
> -- 
> Doug Pardee -- Terak Corp. -- !{hao,ihnp4,decvax}!noao!terak!doug

Why not supply your program's OBJECT code then, and tell your customers
to link it on their machine with their licensed library.

However, that doesn't quite take care of YACC yet.

-- Norman Diamond

UUCP:  {decvax|utzoo|ihnp4|allegra|clyde}!watmath!watdaisy!ndiamond
CSNET: ndiamond%watdaisy@waterloo.csnet
ARPA:  ndiamond%watdaisy%waterloo.csnet@csnet-relay.arpa

"Opinions are those of the keyboard, and do not reflect on me or higher-ups."