From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Pavel PaJaSoft Janousek <janousek@fonet.cz>
Cc: PgSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Error in ECPG and #if...
Date: Wed, 21 Apr 1999 03:36:49 +0000
Message-ID: <371D47D1.49A6B58@alumni.caltech.edu> (raw)
References: <000401be8b46$bd6d96c0$0200a8c0@server.fonet2.cz>
> 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
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: lockhart@alumni.caltech.edu, janousek@fonet.cz
Subject: Re: [INTERFACES] Error in ECPG and #if...
In-Reply-To: <371D47D1.49A6B58@alumni.caltech.edu>
* 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