Re: ECPG include problem

I am trying to compile an application developed on SCO Unix with an Ingres
1.2 database that uses embedded sql. I am having a problem with the
included files.
This code appears in the embedded sql in Ingres:
#include <db1.h>
EXEC SQL INCLUDE SQLCA;
EXEC SQL BEGIN DECLARE SECTION;
EXEC SQL INCLUDE '../include/db2.h';
EXEC SQL END DECLARE SECTION;

The ../include/db2.h file contains lines like
typedef char ComText_t[L_COM_TEXT];
that are defined in db1.h
#define L_COM_TEXT 21 /* Length of pvdef text com parameter.
*/

In porting to psql I have
#include <db1.h>
EXEC SQL INCLUDE sqlca;
EXEC SQL BEGIN DECLARE SECTION;
EXEC SQL INCLUDE ../include/db2;
EXEC SQL END DECLARE SECTION;
but receive the error
../include/db2.h:28: ERROR: parse error at or near "L_COM_TEXT"
If I change
typedef char ComText_t[L_COM_TEXT]; to
typedef char ComText_t[21]; /*value of L_COM_TEXT */
everything is fine. Apparently the preprocessing that Ingres did is not
happening in Postgres. There are over 2000 lines in db2.h, mostly with
constants defined in db1.h. Is there something simple I am overlooking, or
an option to epcg that could allow db2.h to be preprocessed before it is
included?

I am a novice at postgres.
Do not try to solve all life's problems at once -- learn to dread each
day as it comes.

On Wed, 2003-02-19 at 11:24, Mike Alford wrote:
> I am trying to compile an application developed on SCO Unix with an Ingres
> 1.2 database that uses embedded sql. I am having a problem with the
> included files.
> This code appears in the embedded sql in Ingres:
> #include <db1.h>
> EXEC SQL INCLUDE SQLCA;
> EXEC SQL BEGIN DECLARE SECTION;
> EXEC SQL INCLUDE '../include/db2.h';
> EXEC SQL END DECLARE SECTION;
>
> The ../include/db2.h file contains lines like
> typedef char ComText_t[L_COM_TEXT];
> that are defined in db1.h
> #define L_COM_TEXT 21 /* Length of pvdef text com parameter.
> */
>
> In porting to psql I have
> #include <db1.h>
> EXEC SQL INCLUDE sqlca;
> EXEC SQL BEGIN DECLARE SECTION;
> EXEC SQL INCLUDE ../include/db2;
> EXEC SQL END DECLARE SECTION;
> but receive the error
> ../include/db2.h:28: ERROR: parse error at or near "L_COM_TEXT"
> If I change
> typedef char ComText_t[L_COM_TEXT]; to
> typedef char ComText_t[21]; /*value of L_COM_TEXT */
> everything is fine. Apparently the preprocessing that Ingres did is not
> happening in Postgres. There are over 2000 lines in db2.h, mostly with
> constants defined in db1.h. Is there something simple I am overlooking, or
> an option to epcg that could allow db2.h to be preprocessed before it is
> included?
>
> I am a novice at postgres.

To the best of my knowledge, there is no such option. You may want to
try running db2.h through cpp prior to running ecpg. For best results,
you would not want any other headers included--just db1.h and db2.h.

--
Matthew Vanecek
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
********************************************************************************
For 93 million miles, there is nothing between the sun and my shadow except me.
I'm always getting in the way of something...

On Wed, Feb 19, 2003 at 05:24:45PM +0000, Mike Alford wrote:
> everything is fine. Apparently the preprocessing that Ingres did is not
> happening in Postgres. There are over 2000 lines in db2.h, mostly with
> constants defined in db1.h. Is there something simple I am overlooking, or
> an option to epcg that could allow db2.h to be preprocessed before it is
> included?

Ingres preprocessor does parse C and CPP code as well, ecpg does not. It
only parses stuff after an exec sql keyword is found. The only way for
you get this going is to use "exec sql define" instead of "#define" as
the former is parsed an honored by ecpg. Of course you could as well try
running cpp over the files before but that won't always work.

Michael
--
Michael Meskes
Email: Michael(at)Fam-Meskes(dot)De
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!