From: Michael Meskes <meskes@postgresql.org>
To: Mike Alford <mikea@syscon-intl.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ECPG include problem
Date: Fri, 21 Feb 2003 08:14:29 +0100
Message-ID: <20030221071429.GG7378@feivel.fam-meskes.de> (raw)
In-Reply-To: <200302192220.RAA22200@smtp.syscon-intl.com>
References: <200302192220.RAA22200@smtp.syscon-intl.com>
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@Fam-Meskes.De
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
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: meskes@postgresql.org, mikea@syscon-intl.com
Subject: Re: ECPG include problem
In-Reply-To: <20030221071429.GG7378@feivel.fam-meskes.de>
* 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