Re: keyword list/ecpg

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Mike Aubury <mike(dot)aubury(at)aubit(dot)com>, pgsql-hackers(at)postgresql(dot)org, Michael Meskes <meskes(at)postgresql(dot)org>
Subject: Re: keyword list/ecpg
Date: 2008-06-13 14:53:32
Message-ID: 10968.1213368812@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Mike Aubury wrote:
>> Theres also another thing that needs to be decided, which is if the generated
>> ecpg grammer should be developer generated (ie. Michael Meskes runs a script
>> and commits the output), or should be generated for each and every source
>> based installation. I personally would stongly favour the script being a tool
>> for ecpg tool developers and not used as part of a normal installation.

> What happens when a non-Michael developer changes the original gram.y?
> Is he expected to run the script before committing too? That sounds
> brittle to me.

As long as the script is written in Perl and not exceedingly slow,
I see no reason it shouldn't be required to run as part of a build from
CVS. We already require Perl use elsewhere in the build if you're not
working from a tarball.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-06-13 15:08:51 Re: keyword list/ecpg
Previous Message Mike Aubury 2008-06-13 14:53:03 Re: keyword list/ecpg