| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | selkovjr(at)mcs(dot)anl(dot)gov |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: [INTERFACES] esql\c documentation |
| Date: | 1999-06-22 08:46:02 |
| Message-ID: | 19990622104602.A1527@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Mon, Jun 21, 1999 at 08:46:39PM -0400, selkovjr(at)mcs(dot)anl(dot)gov wrote:
> Excuse me -- what's wrong with shift/reduce conflicts? I have over a
> hundred of those in one of my applications.
Having a shift/reduce conflict means that you can find a statement that is
incorrectly parsed. The system will either do a shift (so the statement is
parsed via alternative 1) or do a reduce (parsing alternative 2) but what
you have in mind is certainly only one of these alternatives.
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael(dot)Meskes(at)gmx(dot)net | Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Mount | 1999-06-22 08:55:17 | RE: [INTERFACES] libpq, large Objects |
| Previous Message | Thomas Lockhart | 1999-06-22 06:36:42 | Re: [INTERFACES] esql\c documentation |