"Marko Kreen" <markokr(at)gmail(dot)com> writes:
> How about following patch? I have bison 2.3 and it seems not to do
> global allocation, so it should be fine. There may be early exit
> with elog(ERRROR) inside so I'd like to avoid malloc() itself.
None of our other parsers fool with bison's memory allocation;
why does yours need to?
regards, tom lane