From: Michael Meskes <meskes@postgresql.org>
To: Matthew Vanecek <mevanecek@yahoo.com>
Cc: Postgresql Interfaces List <pgsql-interfaces@postgresql.org>
Subject: Re: ECPG and C++ compilation
Date: Mon, 24 Feb 2003 16:24:58 +0100
Message-ID: <20030224152458.GA2980@feivel.fam-meskes.de> (raw)
In-Reply-To: <1045926883.27169.76.camel@reliant.home.pri>
References: <NDBBLJPIEGAHHANHMMBBEEOGCNAA.dpant@intracom.gr>
<1045926883.27169.76.camel@reliant.home.pri>
On Sat, Feb 22, 2003 at 09:14:43AM -0600, Matthew Vanecek wrote:
> I don't think that will work. I can never get ecpg to recognize
> typedefed structs, even when declaring the typedefed struct within a
> DECLARE SECTION.
Now that I do not understand. What exactly doesn't work? do you have a
small example?
> Probably doing the sizeof calculation within ecpg would be the proper
> way to go, and using that value in the ECPGdo call instead of
> sizeof(whatever). With respect to C++, anyhow. I'm sure the developers
But that would mean you cannot precompile on one machine for usage on
another. Right?
> would accept a patch, but realize that ecpg generates native C code, and
> follows C conventions. C++ may parse the code differently in some
> cases. Your best bet is going to be using the C compiler on these files
> to generate you object code, and your C++ compiler on your native C++
> code, as Peter suggested.
I agree as well.
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, mevanecek@yahoo.com
Subject: Re: ECPG and C++ compilation
In-Reply-To: <20030224152458.GA2980@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