|Commercial LEX/YACC -vs- Flex/Bison email@example.com (todd) (1997-11-13)|
|Re: Commercial LEX/YACC -vs- Flex/Bison firstname.lastname@example.org (1997-11-14)|
|Re: Commercial LEX/YACC -vs- Flex/Bison Stephen_Flanagan@bsginc.com (1997-11-16)|
|Re: Commercial LEX/YACC -vs- Flex/Bison email@example.com (1997-11-16)|
|Re: Commercial LEX/YACC -vs- Flex/Bison firstname.lastname@example.org (Henry Spencer) (1997-11-18)|
|From:||email@example.com (Dwight VandenBerghe)|
|Date:||14 Nov 1997 11:46:19 -0500|
|Organization:||All USENET -- http://www.Supernews.com|
|Keywords:||lex, yacc, comment|
On 13 Nov 1997 23:44:49 -0500, "todd"
>Does anyone have recommendations as to whether the commercially
>available Lex/YACC packages are significantly better than Flex and
>Bison. Specifically, the tools from MKS and Abraxas? I've been using
>Flex and Bison with much success (WinTel platform) and am trying to
>understand the benefits of these packages (which cost $400 - $1000).
If all you want is the basic functionality, then flex and byacc (or
bison) are fine. If you want something more, I highly recommend
Yacc++ from Compiler Resources. I found out about them from our
FAQ, and although the package is not cheap, it is really well
implemented. And it has one of the best manuals I've had the
pleasure of reading, in my 31 years of programming. Five stars.
[Chris Clark, who wrote much of that package, posts here from time to time.
Return to the
Search the comp.compilers archives again.