Re: Oracle grammar ambiguities and conflicts

John Fairhall wrote:
>> I am attempting to write a parser for Oracle 7.3.4 SQL/PLSQL using
>> Visual Parse++ 4.0. I have run into a problem where non-reserved
>> keywords must be included as identifiers, causing millions of conflicts
>> in the grammar. Does anyone have experience with either using VP++
>> or with writing grammars for SQL?
>


matt blackmon wrote:
> Lastly, would a LL grammar be more befitting this problem than a LR?


Don't know if this will help, but I wrote a top-down recursive-descent
parser in Java for SQL-like queries, at:
    http://david.tribble.com/src/java/tribble/parse/sql/QueryParser.java
which is part of my 'tribble.parse.sql' package at:
    http://david.tribble.com/src/java


The parse_operand() and parse_name_expr() methods treat a
keyword as an error when an operand (identifier or literal) is
expected, but they can be modified fairly easily (although you
may give up some syntax checking if you do this).


(My code is open source.)


-drt

Return to the comp.compilers page.
Search the comp.compilers archives again.