Re: Embedded SQL: Putting a guard around included stdio.h for convenience - Mailing list pgsql-interfaces

From Michael Meskes
Subject Re: Embedded SQL: Putting a guard around included stdio.h for convenience
Date
Msg-id 20031008071800.GA11095@feivel.fam-meskes.de
Whole thread Raw
In response to Embedded SQL: Putting a guard around included stdio.h for convenience  (Carsten Klein <carstenklein@yahoo.de>)
List pgsql-interfaces
On Thu, Oct 02, 2003 at 12:57:37AM +0200, Carsten Klein wrote:
> 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 */

As Tom already pointed out it is stdio.h's job to guard against double
inclusion. The ifndef should be listed in stdio.h and certainly is on my
Debian system.

> 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),

Why is it obsolete? 

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: Embedded SQL: Putting a guard around included stdio.h for convenience
Next
From: Stephane Pinel
Date:
Subject: Re: Unresolved extern symbols (solved)