| From: | Ian Lance Taylor <ian(at)airs(dot)com> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Vince Vielhaber <vev(at)michvhf(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [PATCHES] Select parser at runtime |
| Date: | 2001-08-13 17:08:46 |
| Message-ID: | siwv47vqe9.fsf@daffy.airs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> If we want to have both parsers available at runtime we need
> to replace the YY (case-insensitive) prefix in the generated
> files per parser and call the right one from tcop. Now for
> some flex/bison combo's at least the prefix switches (to have
> something different than YY) don't work reliable. There will
> be some global YY-objects left, causing linkage problems.
> That's why PL/pgSQL's scanner/parser's C-code is run through
> sed(1).
This is a solved problem. gdb, for example, links together four
different Yacc-based parsers, without even using bison's -p option.
Ian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-08-13 17:21:53 | Re: Surviving transaction-ID wraparound, take 2 |
| Previous Message | Hiroshi Inoue | 2001-08-13 16:56:31 | Re: PL/pgSQL bug? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2001-08-13 17:33:54 | Re: Re: [PATCHES] Select parser at runtime |
| Previous Message | Gerhard Häring | 2001-08-13 17:03:37 | Fix for fetchone() and fetchmany() in Python interface |