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

From Tom Lane
Subject Re: bool: symbol name collision
Date
Msg-id 16133.1273607226@sss.pgh.pa.us
Whole thread Raw
In response to Re: bool: symbol name collision  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: bool: symbol name collision  (Robert Haas <robertmhaas@gmail.com>)
Re: bool: symbol name collision  (Greg Stark <gsstark@mit.edu>)
List pgsql-bugs
Alex Hunsaker <badalex@gmail.com> writes:
> 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.  We 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.  If 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?

Yeah, it's the implications for 3rd-party modules that make me not want
to do this.  A search & replace on our own code base is one thing, but
when it's positively guaranteed to hit most add-on modules as well,
you need to show a pretty strong benefit from it.  I think the argument
for changing this is too thin to support that.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: bool: symbol name collision
Next
From: Peter Eisentraut
Date:
Subject: Re: bool: symbol name collision