Skip site navigation (1) Skip section navigation (2)

Re: compile bug in HEAD?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nicolas Bazin" <nbazin(at)ingenico(dot)com(dot)au>
Cc: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>,"Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: compile bug in HEAD?
Date: 2002-03-27 06:16:40
Message-ID: 16564.1017209800@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Nicolas Bazin" <nbazin(at)ingenico(dot)com(dot)au> writes:
> It's more warnings than bugs. I also have seen that but not familiar enough
> with bison or yacc to think more of it. Have you got an idea on how to fix
> these warnings?

ecpg's lexer has always generated those warnings, and so has plpgsql's
lexer.  AFAICT the sloppy C code is triggered by use of yylineno.
Suggest griping to the flex authors.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2002-03-27 06:22:09
Subject: SET NOT NULL/DROP NOT NULL patch
Previous:From: Bruce MomjianDate: 2002-03-27 05:35:45
Subject: Re: compile bug in HEAD?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group