Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!mcnc!decvax!ima!esegue!compilers-sender From: chasm@attctc.Dallas.TX.US (Charles Marslett) Newsgroups: comp.compilers Subject: Re: bison/yacc Summary: PD YACC Message-ID: <1989Aug19.161131.1284@esegue.uucp> Date: 19 Aug 89 16:11:31 GMT References: <1989Aug15.192607.4488@esegue.uucp> Sender: compilers-sender@esegue.uucp (John R. Levine) Reply-To: chasm@attctc.Dallas.TX.US (Charles Marslett) Organization: The Unix(R) Connection, Dallas, Texas Lines: 21 Approved: compilers@esegue.segue.bos.ma.us > [Decus yacc was a pirate version of AT&T yacc that Decus (the DEC users' > group) distributed for a while until they realized what it was. I know of > no PD version of yacc and would be surprised to hear of one considering how > much work is involved; every allegedly PD yacc I've ever seen has turned out > to be a pirate copy of AT&T yacc. ... -John] I don't know if this is approriate, but it does sort-of wrap up the issue. A definitely non-AT&T, non-FSF version of yacc was posted to the minix newsgroup earlier this summer. I have self-compiled the parser, and it seems to be about on a par (size, speed, etc.) with the AT&T and FSF parser generators. The author mentioned that it runs rather slowly, but with a reasonable disk cache, I don't see any significant difference in speed (no more than perhaps 2-1), and the code is reputed to have run on a Z80 system at one time! Charles Marslett chasm@attctc.dallas.tx.us -- Send compilers articles to compilers@ima.isc.com or, perhaps, Levine@YALE.EDU { decvax | harvard | yale | bbn }!ima. Meta-mail to ima!compilers-request. Please send responses to the author of the message, not the poster.