Re: Compilation warnings in Lua 5.2.1 (size_t to unsigned int conversion)

[William Sumner <prestonsumner@...>]

On Sep 27, 2012, at 1:05 PM, William Ahern <william@25thandClement.com> wrote:

> Anyhow, point is, at some point people will need to stop equating zero
> compiler warnings with good code, because it will (or already has) passed
> the point where most compiler diagnostics actually flag high-risk
> constructs. Instead, particularly with clang, the diagnostics are just
> someone's idea of good coding style, unrelated to the actual prevalance of
> bugs.

You're moving this into a larger, subjective debate about how you believe other developers should treat warnings. However, nobody has said having no warnings automatically means that the code is good. The issue is specifically about warnings generated by default when compiling Lua in an Xcode project. If the project treats warnings as errors or has a policy of maintaining code that generates no warnings (regardless of your beliefs), the developer will be forced to address it.