Received: from onestone.elsinore.klever.net (root@onestone.elsinore.klever.net [207.175.129.2]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA61343 for ; Tue, 14 Dec 1999 15:21:55 -0500 (EST) (envelope-from sbirch@ironmountainsystems.com) Received: from ironmountainsystems.com ([209.234.201.36]) by onestone.elsinore.klever.net (8.8.7/8.8.0) with ESMTP id NAA23517 for ; Tue, 14 Dec 1999 13:19:10 -0800 Sender: sbirch@onestone.elsinore.klever.net Message-ID: <3856A6CE.324E8242@ironmountainsystems.com> Date: Tue, 14 Dec 1999 12:21:34 -0800 From: Stephen Birch Organization: Iron Mountain Systems, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgreSQL.org Subject: Oops: ecpg changes <> to = (not good) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 #include 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