The only version that worked was 3.4.4. Anything after was breaking even more stuff. I used Gold for many years, and it was a good grief. Switched to Bison and Antlr.
Please stay away from it!
Hi,
I'm implementing a Plsql grammar based on the specification found at this Oracle site: http://docs.oracle.com/cd/E11882_01/server.112/e26088/toc.htm#BEGIN
The goal is to build a powerful plsql editor.
I'm about half way through the project but i can already parse quite complex plsql packages.
The trouble is:
- i had to remove the builtin plsql functions (TO_CHAR, TO_NUMBER... etc) and treat them as generic function calls because the Gold system was using about 5Gb of ram to generate the tables;
- even so, it uses about 2Gb of ram, and takes about 5m to generate the tables - around 1800 DFA states - and analyzes about 50 000 configuration sets;
- parsing a 20 000 lines package takes about 1 minute <- this is impractble.
Question:
Is this the performance expected for such a complex grammar, or am i doing something wrong ? (i've followed the given specification, with adjustments)
Should i have chosen another parsing system? GLR, PEG?
Also the grammar as a few ambiguities which i was unable to solve, does this have impact on performance?
What exactly did you dislike about Version 4 and later?
On Mon, Jan 7, 2013 at 6:25 PM, ki <kizm...@gmail.com> wrote:
> The only version that worked was 3.4.4. Anything after was breaking even
> more stuff. I used Gold for many years, and it was a good grief. Switched to
> Bison and Antlr.
>
> Please stay away from it!
>
> --
> You received this message because you are subscribed to the Google Groups
> "GOLD Parsing System" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/gold-parsing-system/-/fU9ghxJ14ggJ.
>
> To post to this group, send email to gold-pars...@googlegroups.com.
> To unsubscribe from this group, send email to