Suppressing variable hiding warning in Xcode

2009-04-05 Thread Brad O'Hearne
Hey there, I had a few questions about selectively suppressing a certain warning in Xcode. I personally find the warning which pertains to local variables hiding instance variables a real nuisance. For example, if you have a message signature with a parameter name which matches an

RE: Suppressing variable hiding warning in Xcode

2009-04-05 Thread Jeff Laing
variables hiding instance variables a real nuisance. For example, if you have a message signature with a parameter name which matches an instance variable name, and the compiler produces the following message: warning: local declaration of 'variable name' hides instance variable What

Re: Suppressing variable hiding warning in Xcode

2009-04-05 Thread Chris Suter
Hi Brad, On Mon, Apr 6, 2009 at 10:10 AM, Brad O'Hearne br...@bighillsoftware.com wrote: I had a few questions about selectively suppressing a certain warning in Xcode. I personally find the warning which pertains to local variables hiding instance variables a real nuisance. For example, if

Re: Suppressing variable hiding warning in Xcode

2009-04-05 Thread Bill Bumgarner
On Apr 5, 2009, at 5:10 PM, Brad O'Hearne wrote: 1. I get the gist of trying to prevent developers from accidentally hiding variables -- but is this really a major problem? Other than this, is there a compelling reason to keep this warning in tact, and change variable parameter variable

Re: Suppressing variable hiding warning in Xcode

2009-04-05 Thread Bradley S. O'Hearne
All, Thanks for the advice. I everyone on the one extra line of defense rationale. I've worked in languages other than Objective C for years where using variable hiding is common practice, not flagged by the compiler. But you are right, that is only safe for developers who NEVER make a

Re: Suppressing variable hiding warning in Xcode

2009-04-05 Thread Graham Cox
On 06/04/2009, at 11:06 AM, Bill Bumgarner wrote: 2. How do you get Xcode to not produce this warning? Don't. You'll thank yourself for not doing so after spending a few hours wondering why an iVar didn't get updated only to find that a parameter hid the iVar. Given that good advice