Xref: utzoo comp.sources.bugs:784 comp.unix.questions:5723
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!pasteur!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.sources.bugs,comp.unix.questions
Subject: Re: System V yacc / perl problem
Message-ID: <7282@brl-smoke.ARPA>
Date: 18 Feb 88 22:49:21 GMT
References: <1675@van-bc.UUCP> <3328@cbmvax.UUCP> <5096@sdcrdcf.UUCP>
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8
Keywords: yacc perl sysv

In article <5096@sdcrdcf.UUCP> faigin@sdcrdcf.UUCP (Daniel P Faigin) writes:
>The problem is that the output of yacc contains AT&T
>propriatary code (inserted by the yacc program), and so yacc
>output can only be sent to parties with a source license.

At a USENIX long ago, AT&T licensing spokesmen stated the contrary,
that yacc output was free of licensing restrictions.  This should
be checked with them...