Xref: utzoo comp.sources.bugs:780 comp.unix.questions:5704
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!pasteur!ucbvax!hplabs!sdcrdcf!faigin
From: faigin@sdcrdcf.UUCP (Daniel P Faigin)
Newsgroups: comp.sources.bugs,comp.unix.questions
Subject: Re: System V yacc / perl problem
Message-ID: <5096@sdcrdcf.UUCP>
Date: 17 Feb 88 17:03:48 GMT
References: <1675@van-bc.UUCP> <3328@cbmvax.UUCP>
Reply-To: faigin@sdcrdcf.UUCP (Daniel P Faigin)
Organization: Unisys - System Development Group, Santa Monica
Lines: 19
Keywords: yacc perl sysv

In article <3328@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
>It would be helpful if Larry could include the yacc output, with the 
>makefile set up to only redo the yacc run in the critical input files
>changed, but of course this would make the release bigger...

Actually, we discussed this with larry when perl was first being
developed. 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. This
makes posting the program difficult. Hence, the input to yacc is
posted. The way I understand it, you cannot compile perl if you don't
have access to yacc or bison (GNU yacc).

Daniel Faigin (Larry Wall's former officemate)
-- 
W: UNiSYS/Defense Systems/System Development Group
   2400 Colorado MD 91-01;Santa Monica CA 90406;213/829-7511 x6393
H: 8333 Columbus Avenue #17; Sepulveda CA 91343
Email: (uucp) faigin@sdcrdcf.UUCP (arpa) faigin@RDCF.SM.UNISYS.COM