Re: libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved
От | Robert Haas |
---|---|
Тема | Re: libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved |
Дата | |
Msg-id | CA+Tgmoa9YKtbHgpBGd-Jtnz12yxdUjQ8WizUaLJp04r341etuw@mail.gmail.com обсуждение исходный текст |
Ответ на | libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved (Alex Goncharov <alex-goncharov@comcast.net>) |
Ответы |
Re: libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved
|
Список | pgsql-hackers |
On Tue, Dec 13, 2011 at 7:55 AM, Alex Goncharov <alex-goncharov@comcast.net> wrote: > If the above change causes a warning in a client code, so much the > better: the client code is doing something unreasonable like the "*s" > assignment in my example above. Or they just haven't bothered to decorate their entire code-base with const declarations. I suppose it's probably worth doing this, but I reserve the right to be unexcited about it. At a minimum, I dispute the application of the term "painless" to any change involving const. If you want this patch to be considered for application, you should post an updated patch which includes the necessary doc changes and add a link to it here: https://commitfest.postgresql.org/action/commitfest_view/open -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: