Re: Ungraceful handling of fatal flex errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: dom(at)idealx(dot)com
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Ungraceful handling of fatal flex errors
Date: 2001-01-29 14:43:35
Message-ID: 24259.980779415@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

dom(at)idealx(dot)com, dom(at)idealx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-29 14:48:21 Re: new version of contrib-intarray
Previous Message Oleg Bartunov 2001-01-29 14:19:27 Re: new version of contrib-intarray