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

Re: keyword list/ecpg

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>,PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: keyword list/ecpg
Date: 2008-06-04 15:11:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Jun 04, 2008 at 10:21:19AM -0400, Tom Lane wrote:
> Ugh :-(.

This is why I didn't want to go that route. :-)

> I have not spent much time looking at the ecpg grammar, so feel free to
> laugh this off, but I had the impression that all the rules derived from
> the backend grammar have boilerplate action sections (ie, just join the

This is true.

> strings together).  So I was hoping that we could leave the backend's
> .y file more or less as-is, and write a perl script that would go
> through it and replace each { ... } action with a suitable cat_str call,
> which it could build on-the-fly by counting the number of rule tokens.

There is some small magic to know when to have blanks in between and
when not, but that should be doable. 

> Then combine that output with the ecpg-specific rules taken from a
> separate source file.  Obviously there would have to be a few small

This might work. Anyone with good perl knowledge interested? 


Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

In response to


pgsql-hackers by date

Next:From: Hannu KrosingDate: 2008-06-04 15:27:04
Subject: Re: Core team statement on replication in PostgreSQL
Previous:From: Andreas PflugDate: 2008-06-04 15:10:37
Subject: Re: Overhauling GUCS

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