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

From Alex Hunsaker
Subject Re: bool: symbol name collision
Date
Msg-id AANLkTilDSH6gNR2nt3_XeChvZhZYPX5Zg1rfqhaokVVH@mail.gmail.com
Whole thread Raw
In response to Re: bool: symbol name collision  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: bool: symbol name collision  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, May 11, 2010 at 12:42, Robert Haas <robertmhaas@gmail.com> wrote:
> I guess the question that comes to mind for me is how many other
> things fall into this category. =C2=A0We define a lot of symbols like int4
> and int32 that other people could also have defined, and I don't
> really want to s/^/pg/ all of them. =C2=A0If it's really only a question =
of
> renaming bool I could see doing it.

You mean i'd get the pleasure of 'fixing' all my 3rd party C modules?
Not that that is a huge problem, we have broken calling conventions in
most releases...

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: bool: symbol name collision
Next
From: Tom Lane
Date:
Subject: Re: bool: symbol name collision