Re: ECPG include problem - Mailing list pgsql-interfaces

From Christoph Haller
Subject Re: ECPG include problem
Date
Msg-id 3E59F35F.6065B5A7@rodos.fzk.de
Whole thread Raw
In response to ECPG include problem  (Mike Alford <mikea@syscon-intl.com>)
Responses Re: ECPG include problem  (Michael Meskes <meskes@postgresql.org>)
List pgsql-interfaces
>
> 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.
>
Looks like a lack of documentation. Maybe I am wrong, but I could not
find anything about the existence of "exec sql define".

Regards, Christoph




pgsql-interfaces by date:

Previous
From: Matthew Vanecek
Date:
Subject: Using LISTEN/NOTIFY with ecpg
Next
From: Christoph Haller
Date:
Subject: Re: Using LISTEN/NOTIFY with ecpg