Re: bool: symbol name collision - Mailing list pgsql-bugs

From Tom Lane
Subject Re: bool: symbol name collision
Date
Msg-id 3782.1273419324@sss.pgh.pa.us
Whole thread Raw
In response to bool: symbol name collision  (bryanh@giraffe-data.com (Bryan Henderson))
Responses Re: bool: symbol name collision  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
bryanh@giraffe-data.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

pgsql-bugs by date:

Previous
From: Jasen Betts
Date:
Subject: Re: BUG #5448: psql \set does not terminate if variable is referenced recursively
Next
From: Tom Lane
Date:
Subject: Re: reference to undefined macro _MSC_VER