|new language syntax email@example.com (Aleksey Beregov) (2001-08-24)|
|Re: new language syntax firstname.lastname@example.org (2001-08-25)|
|Re: new language syntax email@example.com (2001-08-25)|
|Re: new language syntax firstname.lastname@example.org (2001-09-21)|
|Re: new language syntax email@example.com (HSM) (2001-09-25)|
|Re: new language syntax firstname.lastname@example.org (Ralph Boland) (2001-09-26)|
|Re: new language syntax email@example.com (Joachim Durchholz) (2001-10-06)|
|Re: new language syntax firstname.lastname@example.org (2001-10-20)|
|Re: new language syntax email@example.com (Chris F Clark) (2001-11-05)|
|From:||Ralph Boland <firstname.lastname@example.org>|
|Date:||26 Sep 2001 00:49:43 -0400|
|Organization:||University of New Brunswick|
|References:||01-08-138 01-08-144 01-09-097|
|Keywords:||parse, lex, tools|
|Posted-Date:||26 Sep 2001 00:49:43 EDT|
I am looking for a (free) scanner/parser generator tool I do not know
all the tools available and would like to narrow down the list as much
TGen (written in Smalltalk) mostly satisfies my needs but I would
prefer to find one written in Java or C.
My ideal requirements:
The parser generated should be LALR(1) or LR(1). (A Must) There
shouldn't be any clever tricks to get around grammars that are not
LR(1). If I can't write a LR(1) grammar for my application I lose.
The scanner table should be either a finite state machine or be a LR
based parser table.
Both the scanner table and parser table should be written to a file.
Also any tables such as mappings of Token types to integers should be
written to a file.
The scanner and parser should read these files in order to do their
work. Thus they do not need to change when the scaner/parser tables
etc. are generated for a new language.
It should be possible to write the symbol table and any related tables
of a parsed program to a file as well.
The idea is to be able to use syntactic information about syntacticly
correct programs to do things like language based editing, data
compression, version control etc., systematically and efficiently
using language specific information.
These tools are need to work for any language for which there is a
specification of the language acceptable to the the parser/scanner
Note that I will need access to the source since I will have to modify
what the parser/scanner does and probably make other changes since the
generator tool probably doesn't do exactly what I want.
There should be some language specifications available for some common
languages such as java, C or HTML.
I assume that some version of lex/yacc wuold be best but there are so
many tools out there to choose from.
By the way this is needed for a graduate student project.
Sorry that this was so long.
Return to the
Search the comp.compilers archives again.