Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 (Tek) 9/26/83; site orca.UUCP
Path: utzoo!watmath!clyde!akgua!mcnc!decvax!ittvax!dcdwest!sdcsvax!bmcg!cepu!trwrba!trwrb!sdcrdcf!hplabs!tektronix!orca!andrew
From: andrew@orca.UUCP
Newsgroups: net.unix
Subject: Re: license questions
Message-ID: <822@orca.UUCP>
Date: Fri, 4-May-84 12:55:29 EDT
Article-I.D.: orca.822
Posted: Fri May  4 12:55:29 1984
Date-Received: Tue, 8-May-84 03:33:00 EDT
References: <4606@amd70.UUCP>
Organization: Tektronix, Wilsonville OR
Lines: 18


	"I also seem to recall hearing how applications written with
	YACC included Unix code (in libraries?) and had to be licensed
	but I forget the details.  Could someone refresh my memory?"

The output from YACC includes verbatim the file /usr/lib/yaccpar, which
is considered to be part of Unix.  This means that the executable
program obtained from a source written in YACC includes some of Unix
and so may be distributed only to other Unix licensees.  Ditto for LEX
and /usr/lib/lex/ncform.

This information is from a two-year-old AT&T response to a written
query on this very subject.  The response was unequivocal.  But it's
possible that things have loosened up since then, as they seem to have
for the routines from /lib/libc.a which are loaded because of
compiler-generated calls.

  -- Andrew Klossner   (decvax!tektronix!orca!andrew)      [UUCP]
                       (orca!andrew.tektronix@rand-relay)  [ARPA]