From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Pavel PaJaSoft Janousek <janousek(at)fonet(dot)cz> |
Cc: | PgSQL Interfaces <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | Re: [INTERFACES] Error in ECPG and #if... |
Date: | 1999-04-21 03:36:49 |
Message-ID: | 371D47D1.49A6B58@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel PaJaSoft Janousek | 1999-04-21 10:36:59 | Re: [INTERFACES] ecpg cursors and scope |
Previous Message | Dave Broudy | 1999-04-21 01:46:14 | ecpg cursors and scope |