Skip site navigation (1) Skip section navigation (2)

Re: Erroring out on parser conflicts

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Erroring out on parser conflicts
Date: 2008-11-25 19:15:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tuesday 25 November 2008 15:09:37 Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > While hacking on parser/gram.y just now I noticed in passing that the
> > automatically generated ecpg parser had 402 shift/reduce conflicts.
> > (Don't panic, the parser in CVS is fine.)  If you don't pay very close
> > attention, it is easy to miss this.  Considering also that we frequently
> > have to educate contributors that parser conflicts are not acceptable,
> > should we try to error out if we see conflicts?
> Would "%expect 0" produce the same result in a less klugy way?

Great, that works.  I'll see about adding this to our parser files.

In response to


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2008-11-25 19:27:09
Subject: Re: Exporting PGINTERVALSTYLE prevents access to older server versions
Previous:From: Merlin MoncureDate: 2008-11-25 19:14:10
Subject: Re: [bugfix] DISCARD ALL does not release advisory locks

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group