| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Aubury <mike(dot)aubury(at)aubit(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org> |
| Subject: | Re: keyword list/ecpg |
| Date: | 2008-06-13 15:18:48 |
| Message-ID: | 11311.1213370328@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mike Aubury <mike(dot)aubury(at)aubit(dot)com> writes:
>> What happens when a non-Michael developer changes the original gram.y?
> The same as happens at the moment - nothing...
Wrong answer. The entire point of this work is to get rid of manual
work in updating the ecpg grammar when the main changes. The above
seems about like saying that the build process shouldn't regenerate
gram.c from gram.y --- you're supposed to do that manually.
One of the things I want to have come out of this is that we find out
right away if a main-grammar change breaks ecpg. Right now, any
conflict is not discovered until Michael gets around to syncing the
files, which is often weeks or months later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2008-06-13 15:23:54 | Re: keyword list/ecpg |
| Previous Message | Francesco Biasiol | 2008-06-13 15:09:35 | 8.3.3: uncovered Xml2 functionality |