Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!amdahl!dlb!megatest!djones From: djones@megatest.UUCP (Dave Jones) Newsgroups: comp.lang.misc Subject: Re: increasing yacc states Message-ID: <6244@goofy.megatest.UUCP> Date: 11 Jul 89 14:41:56 GMT References: Organization: Megatest Corporation, San Jose, Ca Lines: 24 (Followups should probably go to comp.compilers, but the moderator is on vacation, so please bear with us.) From article , by mccarrol@topaz.rutgers.edu (Mark C. Carroll ): > Honestly, the best advice I can give you is to not use YACC. The GNU > project wrote a YACC replacement called Bison. It's mostly YACC x > compatible, but it can handle larger, more complicated grammars. > Don't take the following question as a dig at GNU. I'm a satisfied customer. I've used GNU-emacs for over four years. It's now the only editor I feel really comfortable with. I ask the following for information only... A while back, I remember some kind of discussion over the copyright notice on BISON. Do I recall that if you compile it into a program -- a command-interpretter for example, the program is supposed to advertise BISON when it comes up? Or an I dreaming? I also seem to remember some question over whether any program which was prepared using BISON could be shipped without all the GNU baggage, because FSF copyrights the object code resulting from compiling the parser-procedure. I never did hear the last word on it. Can some gnuguru enlighten us?