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

[jean-luc@...]

Le 27 sept. 2012 à 21:45, William Sumner <prestonsumner@me.com> a écrit :

> 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.

I couldn't agree more. This thread has moved very far from my original post.

The whole point of the original message was just to provide a feedback to the Lua team about those 2 narrowing cast warnings in v 5.2.1, in a situation where v 5.2.0 didn't produce any warning with the exact same compiler configuration.

Anyway fixing those is easy and I already did it in my code version.

Discussing about general development policy regarding compiler warnings is an interesting topic, but it is not specific to Lua and can turn into trolling too easily.

Jean-Luc