Re: Further news on Clang - spurious warnings
| От | Peter Geoghegan |
|---|---|
| Тема | Re: Further news on Clang - spurious warnings |
| Дата | |
| Msg-id | CAEYLb_U1YZ+gGmTkY-QmRmK3ZCJQmT7nZ_nOF5kvp5BA06Nn1Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Further news on Clang - spurious warnings (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: Further news on Clang - spurious warnings
Re: Further news on Clang - spurious warnings |
| Список | pgsql-hackers |
On 3 August 2011 12:19, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Right, but the purpose of that check is to defend from programmer error. If > the programmer screws up and calls "PQresStatus(-1)", we want to give an > error, not crash. If you assume that the programmer will only pass a valid > enum constant as parameter, then you might as well remove the if-statement > altogether. I don't think that would be an improvement. Ahh. I failed to consider the intent of the code. Attached patch has a better solution than casting though - we simply use an enum literal. The fact that PGRES_EMPTY_QUERY is the first value in the enum can be safely assumed to be stable, not least because we've even already explicitly given it a corresponding value of 0. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services
Вложения
В списке pgsql-hackers по дате отправления: