Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mimsy!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: C license agreements
Message-ID: <6146@brl-smoke.ARPA>
Date: Wed, 22-Jul-87 02:31:21 EDT
Article-I.D.: brl-smok.6146
Posted: Wed Jul 22 02:31:21 1987
Date-Received: Fri, 24-Jul-87 01:48:45 EDT
References: <8387@brl-adm.ARPA>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 17

In article <8387@brl-adm.ARPA> PEPRBV@cfaamp.bitnet writes:
>Now, what about a shareware  program  where the marketing  is the
>opening screen of the program?   This both must and must not have
>CI's copyright notice.

I suppose that contradiction proves that you're not allowed to
distribute such software.  You really agreed to those terms??

Some applications really do need total control of all I/O activity
that occurs when they run, and spurious output (for example, printing
compiler vendor copyright notices) will break them.  I personally am
so irked at ANY run-time behavior that I did not put in my code that
I will not buy or use such compiler implementations, and I urge you
to adopt the same policy (and to let the vendors hear about it).

I think Ken & Dennis would have croaked anybody who tried to make
UNIX utilities print out identifying messages etc.