|Visual Parse 3.0: is it OK for me ? firstname.lastname@example.org (1999-03-05)|
|Re: Visual Parse 3.0: is it OK for me ? email@example.com (1999-03-06)|
|Re: Visual Parse 3.0: is it OK for me ? firstname.lastname@example.org (Markus Kohler) (1999-03-09)|
|Re: Visual Parse 3.0: is it OK for me ? email@example.com (1999-03-09)|
|Re: Visual Parse 3.0: is it OK for me ? firstname.lastname@example.org (Eddy Poullet) (1999-03-22)|
|Re: Visual Parse 3.0: is it OK for me ? email@example.com (Darren Forcier) (1999-03-23)|
|From:||Darren Forcier <firstname.lastname@example.org>|
|Date:||23 Mar 1999 12:34:58 -0500|
I just recently started playing with the Visual Parse++ 3.0 eval to
create an SQL parser in Delphi. It took me a while to get it working,
but so far it appears to be pretty good. Up until now I have mostly
played with a Turbo Pascal-generating variation of Lex and Yacc that
were decent but lacked up to date Delphi code generation support.
The main thing I like about Visual Parse++ is that it comes with
sample scripts for a lot of the major stuff I am interested in like
SQL and HTML grammars. The things I don't like about it are it's very
sparse documentation (a single, one line sentance for each bullet item
in the tutorial and reference) and some of the weird antics of the
IDE. (although being able to step through a parse visually is pretty
One other thing I really like is how the Lex and Yacc specifications
are combined into one (albeit proprietary but Lex/Yacc-like enough)
specifications language so you can generate from a single file instead
of generating the Lexer and Yacc modules separately and then having to
manually glue them together into a working module.
> I use an evaluation version of VP3.0.
> It seems pretty bugged, and I really hesitate using it for my project.
> - Does anyone have some serious working experience with VP3.0 ?
Return to the
Search the comp.compilers archives again.