From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Danny Milosavljevic <danny(dot)milosavljevic(at)fabalabs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq-fe: PQgetvalue() ? |
Date: | 2006-11-25 00:10:53 |
Message-ID: | 200611250010.kAP0AsO17512@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > This has been saved for the 8.3 release:
>
> > Danny Milosavljevic wrote:
> >> Shouldn't the return type of "PQgetvalue" be "const char*", then?
>
> The pluses and minuses of const-ifying libpq's API have been discussed
> before. If we were working in a green field we'd no doubt do it, but
> I'm not sure that users would thank us for breaking their existing
> working code. Adding a "const" to a function result value has direct
> impact on calling applications...
OK, I was afraid of that. Removed from the 8.3 queue.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2006-11-25 00:28:28 | Re: Avg performance for int8/numeric |
Previous Message | Tom Lane | 2006-11-24 23:52:03 | Re: libpq-fe: PQgetvalue() ? |