From: Carsten Klein <carstenklein@yahoo.de>
To: pgsql-interfaces@postgresql.org
Subject: Embedded SQL: Putting a guard around included stdio.h for convenience
Date: Thu, 02 Oct 2003 00:57:37 +0200
Message-ID: <3F7B5BE1.3000309@yahoo.de> (raw)
Hi all,
I have just tried to compile an application consisting of multiple
modules, each of them encapsulation access to a single table of
the default database, using embedded sql.
Well, until now, I have had problems with stuff being declared twice
(from stdio.h and successively included include files by stdio.h),
since postgres sources seemingly do not put a guard around the include
statement.
what i mean is, please, do include the following:
#ifndef _STDIO_H
#include <stdio.h>
#endif /* _STDIO_H */
This seemingly is not being generated by the ecpg or included in the
header files being included.
And while we are at it, although I personally think that Embedded SQL is
quite obsolete by now (but we have to do this stuff in school, perhaps
I'm wrong),
please check other parts of your source referencing (including) external
include files, where there is no guard around the include statement. It
makes things
tedious and nearly impossible to solve, when they are not there...
Thanks.
Carsten Klein
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: carstenklein@yahoo.de
Subject: Re: Embedded SQL: Putting a guard around included stdio.h for convenience
In-Reply-To: <3F7B5BE1.3000309@yahoo.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