Path: utzoo!attcan!uunet!mcvax!unido!sbsvax!greim
From: greim@sbsvax.UUCP (Michael Greim)
Newsgroups: comp.sources.d
Subject: Re: v16i034: Larry Wall's Configure
Summary: you can use bison to 'yacc' perl
Message-ID: <642@sbsvax.UUCP>
Date: 11 Nov 88 08:57:10 GMT
References: <0@andrew> <3100001@nixpbe>
Organization: Universitaet des Saarlandes, Saarbruecken, West Germany
Lines: 26

In article <3100001@nixpbe>, kebsch@nixpbe.UUCP writes:
< 
< Jay Libove wrote:
< 
< > Well, Larry (for the first time I've ever seen) made a number of very
< > very bad assumptions in his configure distribution.
< >
< > 1) that you have Perl. Perl doesn't run on 80286 machines. Not at all.
< 			 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< That's wrong! I yacc'ed perl.y on a 32 bit machine and compiled
< Perl-2.0, Patchlevel-14 on a 80286 machine. It runs pretty good and
< I have no problems! My Operatingsystem is UNIX Sytem V Rel-2 (Microport).
< So don't flame on Larry Wall, flame on SCO Xenix SysV/286 v2.2.1.
< 
I had a problem to yacc perl on my system, too. Like Jay I yacc'ed perl on
a 32 bit machine.
Recently I ported bison and tested it, among other things, on perl.y.
It worked ok.  And if you are coming up against some built-in limits in bison
you can always change them.

	-mg
-- 
email : greim@sbsvax.informatik.uni-saarland.dbp.de
  (some mailers might not like this. Then use greim@sbsvax.uucp)
  or  : ...!uunet!unido!sbsvax!greim
# include <disclaimers/std.h>