Can I turn off the Xcode's unused variable warnings?
Don't. Fix the warnings. Warnings are your friend. They show you bugs in your code. If you get warnings, fix the reason for the warning.
If you put all your declarations in a header file, you don't get the warnings.
Okay, look. Let's put things into perspective here, people. There are warnings and then there are warnings. Converting a float to pointer without a castyeah, that's something I want to know about and almost certainly need to fix. Unused variables? Please. What's the risk here, that I run out of stack space? Whatever.
If the guy knows what he's doing, and has explained exactly why he wants to do it, why hassle him about a simple question? Because it doesn't meet your arbitrary standards for what is considered proper? Either get off your high horse and help him with the question he asked, or keep your snobbish comments about what you consider to be best practice to yourselves.
Converting a float to pointer without a cast—yeah, that's something I want to know about and almost certainly need to fix.
Okay, look. Let's put things into perspective here, people. There are warnings and then there are warnings.
If the guy knows what he's doing, and has explained exactly why he wants to do it, why hassle him about a simple question?
Unused variables? Please. What's the risk here, that I run out of stack space? Whatever.
Don't. Fix the warnings. Warnings are your friend. They show you bugs in your code. If you get warnings, fix the reason for the warning.
Why on earth would you keep unused variables in the first place?
Nope. LLVM is smart enough to remove these code paths from an optimized release build....you run into performance hits.
I want the reason for the warnings in my code. Therefore I do not wish to "fix" them and make my code worse. You can ruin your own code if you wish, but don't recommend damaging mine.