Related articles |
---|
Lex/Yacc (Flex/Bison): Obtaining a list of the next possible tokens f hundhaus@hawaii.edu (Chris Hundhausen) (2002-10-13) |
Re: Lex/Yacc (Flex/Bison): Obtaining a list of the next possible token gordan.sikic@inet.hr (Gordan Sikic) (2002-10-18) |
From: | "Gordan Sikic" <gordan.sikic@inet.hr> |
Newsgroups: | comp.lang.c++,comp.compilers |
Date: | 18 Oct 2002 23:05:29 -0400 |
Organization: | Iskon Internet d.d. |
References: | 02-10-029 |
Keywords: | parse, errors |
Posted-Date: | 18 Oct 2002 23:05:29 EDT |
Hi,
> Is there anyone out there who has done this and could give me some
> advice? I've heard that ANTLR has this functionality, but I'd prefer
> not to convert to ANTLR unless I have to. (If you'd done this in
> ANTLR, please respond too, because I may have to convert to ANTLR if
> flex/bison won't do the job.)
In the company I work for, we were implementing batch processing
language, and tried to use flex/bison combination, but we _did_ switch
to ANTLR and we never regreted. The code gnerated with antlr was C++
(which we needed), no static/global variables, and debugging was much
easier. If you can spare some time to learn differences, switch to
antlr :).
ciao,
Gordan
Return to the
comp.compilers page.
Search the
comp.compilers archives again.