Re: bool: symbol name collision

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Bryan Henderson <bryanh(at)giraffe-data(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: bool: symbol name collision
Date: 2010-05-09 16:58:06
Message-ID: 5805.1273424286@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On sn, 2010-05-09 at 11:35 -0400, Tom Lane wrote:
>> ... we consider building server extensions with C++ to be
>> unsupported anyway.

> Um, our code has

> #ifndef __cplusplus

> #ifndef bool
> typedef char bool;
> #endif

> etc.

Yeah, I know those #if's are there, but whether they actually do
anything useful is highly questionable. There is no reason to assume
that a compiler's built-in version of bool will be bit-compatible with
ours. And changing the width of bool is guaranteed to Not Work.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2010-05-09 17:01:03 Re: bool: symbol name collision
Previous Message Peter Eisentraut 2010-05-09 16:48:59 Re: bool: symbol name collision