Oops: ecpg changes <> to = (not good)

From: Stephen Birch <sbirch(at)ironmountainsystems(dot)com>
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Oops: ecpg changes <> to = (not good)
Date: 1999-12-14 20:21:34
Message-ID: 3856A6CE.324E8242@ironmountainsystems.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

In the process of cleaning up some memory leaks in the cvs tree, I
discovered that
the checked in version of ecpg interperates <> as =:

For example, if you run ecpg on the following:

test()
{
exec sql
select xxx from yyy where zzz <> ppp;
}

You get this output:

/* Processed by ecpg (2.6.11) */
/* These two include files are added by the preprocessor */
#include <ecpgtype.h>
#include <ecpglib.h>

test()
{
{ ECPGdo(__LINE__, NULL, "select xxx from yyy where zzz = ppp
",
ECPGt_EOIT, ECPGt_EORT);}
#line 5 "t.pgc"

}

Note that zzz <> ppp has been changed to zzz = ppp. This is not broken
in 6.5.3.

Not good.

I would debug this myself, but do not understand lex and yacc well
enough yet.

Steve

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Brian Haney 1999-12-14 20:36:01 RE: access97-Recordset not updatable
Previous Message Matthew Hagerty 1999-12-14 19:13:04 Backend core dump, Please help, Urgent!