Re: Commercial LEX/YACC -vs- Flex/Bison

Stephen_Flanagan@bsginc.com (Stephen Flanagan)
16 Nov 1997 22:48:03 -0500

          From comp.compilers

Related articles
Commercial LEX/YACC -vs- Flex/Bison todd_tomlinson@emeraldsolutions.com (todd) (1997-11-13)
Re: Commercial LEX/YACC -vs- Flex/Bison dwight@pentasoft.com (1997-11-14)
Re: Commercial LEX/YACC -vs- Flex/Bison Stephen_Flanagan@bsginc.com (1997-11-16)
Re: Commercial LEX/YACC -vs- Flex/Bison daniel@dittmar.net (1997-11-16)
Re: Commercial LEX/YACC -vs- Flex/Bison henry@zoo.toronto.edu (Henry Spencer) (1997-11-18)
| List of all articles for this month |
From: Stephen_Flanagan@bsginc.com (Stephen Flanagan)
Newsgroups: comp.compilers
Date: 16 Nov 1997 22:48:03 -0500
Organization: Compilers Central
References: 97-11-080
Keywords: yacc, lex
X-Conversion-ID: <PU-NOTES.2207.879624795.13280>

        I had an "issue" a few years ago with Abraxas's pcyacc accepting
input whereas standard yacc ( correctly ) reported an error. I worked
for a small, commercial product company at the time and the bug was
reported by an important customer. As such, I didn't take the time to
study and document the problem but rather I sent pcyacc to the land of
broken toys. ;)


        Despite this, I believe Abraxas is a great company with great
products.


My message is simply to encourage people using "yacc-alikes" to
periodically validate it against the tried-and-true yacc.


        While I use yacc quite a bit, I haven't used lex since
college. Using lex to scan tokens is akin to using a robot arm and a
nail gun to hang a picture in your living room; it's a superfluous
level of abstraction. Parser generators on the other hand have saved
millions of man-years...
[When the robot arm costs no more than a hammer and is considerably less
likely to land on your thumb, I think it's not a bad tool. -John]


--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.