Re: bool: symbol name collision

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bryanh(at)giraffe-data(dot)com (Bryan Henderson)
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: bool: symbol name collision
Date: 2010-05-09 15:35:24
Message-ID: 3782.1273419324@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

bryanh(at)giraffe-data(dot)com (Bryan Henderson) writes:
> The interface header files for Postgres server extensions define "bool",
> but that name is commonly used by other parts of user code, including
> by standards (C99, C++). That causes, at best, compile failures.

> If Postgres has to define a boolean type in public header files, it should
> use a name that won't collide, like postgres_bool.

Sorry, this isn't going to happen. It would break far too much existing
code, and we consider building server extensions with C++ to be
unsupported anyway.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-05-09 16:25:15 Re: reference to undefined macro _MSC_VER
Previous Message Jasen Betts 2010-05-09 10:58:35 Re: BUG #5448: psql \set does not terminate if variable is referenced recursively