From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Bryan Henderson <bryanh(at)giraffe-data(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: bool: symbol name collision |
Date: | 2010-05-11 19:47:06 |
Message-ID: | 16133.1273607226@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> On Tue, May 11, 2010 at 12:42, Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-05-11 20:15:17 | Re: bool: symbol name collision |
Previous Message | Alex Hunsaker | 2010-05-11 19:09:43 | Re: bool: symbol name collision |