Jan Wieck <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
