From: Stephen Birch <sbirch@ironmountainsystems.com>
To: pgsql-interfaces@postgreSQL.org
Subject: Oops: ecpg changes <> to = (not good)
Date: Tue, 14 Dec 1999 12:21:34 -0800
Message-ID: <3856A6CE.324E8242@ironmountainsystems.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: sbirch@ironmountainsystems.com
Subject: Re: Oops: ecpg changes <> to = (not good)
In-Reply-To: <3856A6CE.324E8242@ironmountainsystems.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox