Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [5 earlier articles] |
| Re: Oracle grammar ambiguities and conflicts DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2006-01-12) |
| Re: Oracle grammar ambiguities and conflicts drikosv@otenet.gr (Evangelos Drikos) (2006-01-12) |
| Oracle grammar ambiguities and conflicts mark.thiehatten@bibit.com (Mark Thiehatten) (2006-01-12) |
| Re: Oracle grammar ambiguities and conflicts cfc@shell01.TheWorld.com (Chris F Clark) (2006-01-17) |
| Re: Oracle grammar ambiguities and conflicts mattblackmon@hotmail.com (Matt Blackmon) (2006-01-17) |
| Re: Oracle grammar ambiguities and conflicts david@tribble.com (David R Tribble) (2006-01-17) |
| Re: Oracle grammar ambiguities and conflicts parsersinc@earthlink.net (SLK Parsers) (2006-01-19) |
| Re: Oracle grammar ambiguities and conflicts parsersinc@earthlink.net (SLK Parsers) (2006-01-19) |
| Re: Oracle grammar ambiguities and conflicts parsersinc@earthlink.net (SLK Parsers) (2006-01-20) |
| From: | "SLK Parsers" <parsersinc@earthlink.net> |
| Newsgroups: | comp.compilers |
| Date: | 19 Jan 2006 01:08:05 -0500 |
| Organization: | Parsers Inc. |
| References: | 01-07-118 06-01-029 06-01-034 |
| Keywords: | SQL, parse |
| Posted-Date: | 19 Jan 2006 01:08:05 EST |
>Generally the cleanest solution is:
>create a non-terminal id which accepts all the keywords (you may have
>done this) and use it in place of your token ID.
And applicable to top-down parsing as well. I used this technique
successfully on a large commercial translator. But it does require some
parsing/grammar knowledge.
The SLK parser generator: http://home.earthlink.net/~slkpg/
Return to the
comp.compilers page.
Search the
comp.compilers archives again.