Re: Latest SQLite vs. Xcode's Analyze : 61 issues
Re: Latest SQLite vs. Xcode's Analyze : 61 issues
- Subject: Re: Latest SQLite vs. Xcode's Analyze : 61 issues
- From: Aaron Montgomery <email@hidden>
- Date: Sat, 22 Sep 2012 14:31:15 -0700
On Sep 22, 2012, at 12:26 PM, 👾 <email@hidden> wrote:
>>> See item #17 in the SQLite FAQ: <http://www.sqlite.org/faq.html#q17>:
>>
>> Thank you, Jens. After reading that, I conclude that sqlite.org is not going to be impressed if I spend a day submitting patches to suppress Xcode Analyze warnings.
>
>
> That FAQ entry strikes me as either way outdated or just snide. Anyone that thinks gcc is the only compiler that matters these days is... out of touch. And while they ostensibly acknowledge the importance of compiler warnings, what they really seem to be saying is that functional testing obviates the need for them. Patently false.
I don't know any of the SQLite developers, so it is possible that the remark was intended to be snide, but I didn't read it that way. I read it as:
We know you may get warnings, but we have a strong suite of functional tests and we eliminate all the compiler warnings for the systems on which we develop.
Remembering when I was testing websites with a number of browsers on a number of different operating systems to make sure that everything worked with everyone, what I read as implied was:
We just don't have the resources to eliminate all compiler warnings on all possible compiler setups, sorry.
As I said, I don't know the developers, but I would guess that they would appreciate patches which cleaned up the build for clang, but none of them are currently building with clang and they don't have the time to shift to a new compiler to quell those warnings themselves.
Aaron
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden