Re: Ungraceful handling of fatal flex errors - Mailing list pgsql-hackers

dom@idealx.com, dom@idealx.com writes:
>> #define fprintf(file,fmt,msg)  elog(FATAL, "%s", (msg))

>   Meaning no disrespect : yuck... IMHO this is asking for trouble
> whenever someone decides to use another yacc.

This is flex, not yacc, and our lexer has been flex-only for a long
time.  It's possible that the hack would break in a future version
of flex, but I doubt it.  What else is a lexer going to use fprintf
for?
        regards, tom lane