yacc: public domain?

[Doug Pardee]

> 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.  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!

A software house that I once worked for sold a package which was
written in IBM OS/370 COBOL.  Because the COBOL compiler being
sold by IBM is a copyrighted and proprietary package, and it
relies heavily on the subroutine library, we had to go to GREAT
pains to stay legal.  Back before the courts ordered IBM to
"unbundle" software, they did have a COBOL compiler which was
public domain.  So we had to get a copy of that, even though it
was 15 years out of date, produced crummy code, and was full of bugs.

A company that I worked for recently was developing a package for
the IBM PC using C.  They chose Computer Innovations' C compiler
over the more common Lattice compiler because of one thing:  Computer
Innovations explicitly authorizes (in writing) sale of programs
containing modules from their subroutine library, without requiring
notification, permission nor royalty.

Copyright infringement on compilers' subroutine libraries IS taken
seriously.
-- 
Doug Pardee -- Terak Corp. -- !{hao,ihnp4,decvax}!noao!terak!doug