Re: Re: [PATCHES] Select parser at runtime - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [PATCHES] Select parser at runtime
Date
Msg-id 16777.997712604@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [PATCHES] Select parser at runtime  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Jan Wieck <JanWieck@Yahoo.com> writes:
>     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).

The only reason plpgsql's parser is still run through sed is that
I haven't gotten around to changing it ;-).  The main system has
depended on -P for awhile, and we've seen no reports of trouble.

(This is not unrelated to the fact that we now ship pre-yacced and
pre-lexed .c files, no doubt.  Only people who pull from CVS ever
rebuild the files at all, and we tell them they must use up-to-date
flex and bison.  This policy seems to work a lot better than the old
way of trying to work with whatever broken tools a particular platform
might have...)
        regards, tom lane


pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: AW: Re: OID wraparound: summary and proposal
Next
From: Alex Avriette
Date:
Subject: drop-in-ability (was: RE: Re: [PATCHES] Select parser a t runtime )