|Creating an interpreter for a Logo-like language on MacOS X firstname.lastname@example.org (Erika) (2003-03-30)|
|Re: Creating an interpreter for a Logo-like language on MacOS X email@example.com (2003-03-30)|
|Re: Creating an interpreter for a Logo-like language on MacOS X firstname.lastname@example.org (2003-03-30)|
|Re: Creating an interpreter for a Logo-like language on MacOS X email@example.com (Erica Mackenzie) (2003-04-05)|
|From:||firstname.lastname@example.org (Hans Aberg)|
|Date:||30 Mar 2003 21:17:31 -0500|
|Posted-Date:||30 Mar 2003 21:17:31 EST|
Erika <email@example.com> wrote:
>: - Which kind of parsing algorithm would to be most appropriate for my
> needs, LR, LALR, top-down, bottom-up, or which, how and why <g>?
As you are designing your own language, it makes little difference
what parsing algorithm you are using: These algorithms are different
in the amount of grammars the accept, but say LALR plus the usual
lexer/parser tweaks are sufficient for most "normal" languages. The
problem arises if you have a given language, and it contains
constructs that must be tweaked in exotic ways.
LALR(1) ("lookahead LR") is a compacted form of LR(1), which combines
different states on the expense of some grammar generality and error
handling (when an error occurs, some extra reductions may be inserted
Look into books on parsing -- see the comp.compilers FAQ for more info.
>: - For a parser-generator/ Tree - Walker (please pardon any imprecise
> terminology - I am still reading, studying and learning) - would Eli,
> Bison, Yacc, PCCTS or ANTLR best suit my needs? as I said before,
> I don't really want an object code output.
Flex/Bison are currently updated an developed, and should be good for
outputting C code:
Help-flex mailing list
I am not sure Yacc is alive, even though there is a "Berkeley Yacc", which
originates with same guy, Robert Corbett, who wrote Bison.
Hans Aberg * Anti-spam: remove "remove." from email address.
* Email: Hans Aberg <firstname.lastname@example.org>
* Home Page: <http://www.math.su.se/~haberg/>
* AMS member listing: <http://www.ams.org/cml/>
[Yacc is quite alive. There haven't been any new versions lately because
there haven't been any new bugs. -John]
Return to the
Search the comp.compilers archives again.