Received: from localhost.jpl.nasa.gov (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.1) with ESMTP id XAA05143 for ; Tue, 20 Apr 1999 23:36:35 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost.jpl.nasa.gov (8.8.7/8.8.7) with ESMTP id DAA08100; Wed, 21 Apr 1999 03:36:49 GMT Sender: lockhart@localhost.jpl.nasa.gov Message-ID: <371D47D1.49A6B58@alumni.caltech.edu> Date: Wed, 21 Apr 1999 03:36:49 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Pavel PaJaSoft Janousek CC: PgSQL Interfaces Subject: Re: [INTERFACES] Error in ECPG and #if... References: <000401be8b46$bd6d96c0$0200a8c0@server.fonet2.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > ECPG don't know C/C++ preprocessing directives such as #if, #ifdef > etc... > I think, that this is wrong, that ECPG use as comment only /* and // > comment. Construction such as #if 0 is very common way to disable some > source and enable this later... - mainly in debugging proces, of cource. ... but this is not common for ESQL preprocessors. The problem is that the preprocessor runs before the C/C++ preprocessor, which is the step which actually handles the #if constructs. ecpg has no knowledge of those constructs. Remember that to do those correctly one must also resolve all other preprocessor kinds of things, like #include directives. - Tom -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California