Skip site navigation (1) Skip section navigation (2)

Re: Embedded SQL: Putting a guard around included stdio.h for convenience

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Carsten Klein <carstenklein(at)yahoo(dot)de>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Embedded SQL: Putting a guard around included stdio.h for convenience
Date: 2003-10-08 07:18:00
Message-ID: 20031008071800.GA11095@feivel.fam-meskes.de (view raw or flat)
Thread:
Lists: 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(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

pgsql-interfaces by date

Next:From: Stephane PinelDate: 2003-10-08 09:36:18
Subject: Re: Unresolved extern symbols (solved)
Previous:From: Tom LaneDate: 2003-10-08 03:16:29
Subject: Re: Embedded SQL: Putting a guard around included stdio.h for convenience

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group