Re: libpq: make PGresult* "const" in PQcmdStatus()/PQcmdTuples()?
| От | Tom Lane |
|---|---|
| Тема | Re: libpq: make PGresult* "const" in PQcmdStatus()/PQcmdTuples()? |
| Дата | |
| Msg-id | 859822.1734796591@sss.pgh.pa.us обсуждение |
| Ответ на | libpq: make PGresult* "const" in PQcmdStatus()/PQcmdTuples()? (Jeroen Vermeulen <jtvjtv@gmail.com>) |
| Ответы |
Re: libpq: make PGresult* "const" in PQcmdStatus()/PQcmdTuples()?
Re: libpq: make PGresult* "const" in PQcmdStatus()/PQcmdTuples()? |
| Список | pgsql-interfaces |
Jeroen Vermeulen <jtvjtv@gmail.com> writes:
> Any objections to changing these two libpq functions' PGresult* parameters
> to be const?
> So "char * PQcmdStatus(PGresult *)" would become "char *PQcmdStatus(const
> PGresult *)", and "char *PQcmdTuples(PGresult *)" would become "char
> *PQcmdTuples(const PGresult *)".
Both of those return pointers to res->cmdStatus, so it would not make
any sense to const-ify the argument unless you also const-ify the
result; which would cause compiler warnings for users. I'm pretty
sure we've explicitly rejected making this change for that reason.
regards, tom lane
В списке pgsql-interfaces по дате отправления: