| From: | "McDevitt, Charles" <Charles(dot)McDevitt(at)emc(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)mail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parser Cruft in gram.y |
| Date: | 2012-12-20 23:12:55 |
| Message-ID: | 55FBC2C083A01C47BF5E0F1FF7F416BC30DF2DE1@MX103CL02.corp.emc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Another way of attack along these lines might be to use the %glr-parser
> and then try to cut back on all those redundant rules that were put in
> to avoid conflicts. The number of key words categories and such could
> perhaps also be reduced that way.
>
> Of course, this is mostly speculation.
>
>
The GLR output from Bison is licensed under the GPL (unlike the LALR output).
So using Bison's GLR mode isn't an option.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-20 23:16:42 | Re: Parser Cruft in gram.y |
| Previous Message | Joshua Berkus | 2012-12-20 22:30:32 | Re: Feature Request: pg_replication_master() |