On Sat, May 30, 2009 at 11:36 PM, Eric Hermanson zmons...@mac.com wrote:
Yes Mike, you ask a very pertinent question.
First I'm looking for a source-time (not compile-time) monitor that would
alert me to potential code problems as I type.
Seems like this would have to be *extremely*
On 31/05/2009, at 11:38 AM, Gwynne Raskind wrote:
Not to mention I haven't yet figured out a way to apply
__attribute__((unused)) to an ObjC method parameter. I just get a
pile of syntax errors, or it gets applied to the function instead of
the parameters.
Just use #pragma
On Fri, May 29, 2009 at 11:37 PM, Gwynne Raskind
gwy...@darkrainfall.org wrote:
In short, you can't get this warning in a Debug-style build unless you want
to sabotage your debugging efforts by adding optimization.
Your best workaround for this is probably to use the Clang static
analyzer
On 30-May-09, at 8:14 AM, cocoa-dev-requ...@lists.apple.com wrote:
Is there a way to tune xCode so that it warns you of these types of
potential problems (and more)?
Here's what I've got in my standard base .xcconfig right now.
// C Only Warnings
TW_GENERAL_OTHER_CFLAGS = -Wdiv-by-zero
On Sat, 30 May 2009 13:22:08 +1000, Graham Cox
graham@bigpond.com wrote:
On 30/05/2009, at 1:13 PM, Eric Hermanson wrote:
Is there a way to tune xCode so that it warns you of these types of
potential problems (and more)? The Java development environment
I've been using for the past
Thanks for that list.
Regarding your choice of
GCC_WARN_UNUSED_PARAMETER = YES
How do you get around the fact that you often get warnings for
delegate methods you are forced to implement where you don't ever use
given parameter(s)? Do you use a #pragma GCC diagnostic ignored ...
On 30-May-09, at 5:31 PM, Eric Hermanson wrote:
Thanks for that list.
Regarding your choice of
GCC_WARN_UNUSED_PARAMETER = YES
How do you get around the fact that you often get warnings for
delegate methods you are forced to implement where you don't ever
use given parameter(s)?
You also have the unused attribute:
http://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Variable-Attributes.html
--Kyle Sluder
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
On 30-May-09, at 6:04 PM, Kyle Sluder wrote:
You also have the unused attribute:
http://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Variable-Attributes.html
--Kyle Sluder
That's out because I commonly have to share code with Windows compilers.
... although much less commonly now that I'm about
On May 30, 2009, at 9:11 PM, Alex Curylo wrote:
You also have the unused attribute:
http://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Variable-Attributes.html
That's out because I commonly have to share code with Windows
compilers.
... although much less commonly now that I'm about 80% focused on
On Sat, May 30, 2009 at 6:38 PM, Gwynne Raskind gwy...@darkrainfall.org wrote:
On May 30, 2009, at 9:11 PM, Alex Curylo wrote:
You also have the unused attribute:
http://gcc.gnu.org/onlinedocs/gcc-3.1.1/gcc/Variable-Attributes.html
That's out because I commonly have to share code with
The problem I have with this GCC __attribute__(unused) thing is that
it does not result in an error if you actually end up using the
attribute (as I would expect it should). If it went that extra step I
would find it more useful than doing just (void)param..., but since it
doesn't, I
On Sat, May 30, 2009 at 6:54 PM, Eric Hermanson zmons...@mac.com wrote:
Thanks for all the input. It would be nice if xCode not only allow an
easy-to-use configuration panel for all GCC warnings (not just some), but
also if xCode would parse source code on the fly to notify of
On Sat, May 30, 2009 at 9:54 PM, Eric Hermanson zmons...@mac.com wrote:
Thanks for all the input. It would be nice if xCode not only allow an
easy-to-use configuration panel for all GCC warnings (not just some), but
also if xCode would parse source code on the fly to notify of
Yes Mike, you ask a very pertinent question.
First I'm looking for a source-time (not compile-time) monitor that
would alert me to potential code problems as I type.
Second, to get an idea of the code inspection capabilities of the Java
IDE I've been using for the past 8 years, see:
On Sat, 30 May 2009 20:31:36 -0400, Eric Hermanson zmons...@mac.com
wrote:
Thanks for that list.
Regarding your choice of
GCC_WARN_UNUSED_PARAMETER = YES
How do you get around the fact that you often get warnings for
delegate methods you are forced to implement where you don't ever
I am periodically bitten by EXC_BAD_ACCESS memory problems that are
sometimes hard to find. One that just occurred was that I was
mistakenly returning an un-initialized local variable from a method
(i.e.
NSObject myObject;
...
... some if-statements
...
return myObject; // I should
On 30/05/2009, at 1:13 PM, Eric Hermanson wrote:
Is there a way to tune xCode so that it warns you of these types of
potential problems (and more)? The Java development environment
I've been using for the past several years (Jetbrains IDEA) has
unbelievably fantastic code-editing and
Thank You. I also just found this useful web page based on your
feedback:
http://developer.apple.com/TOOLS/xcode/staticanalysis.html
On May 29, 2009, at 11:22 PM, Graham Cox wrote:
On 30/05/2009, at 1:13 PM, Eric Hermanson wrote:
Is there a way to tune xCode so that it warns you of
On May 29, 2009, at 11:22 PM, Graham Cox wrote:
Is there a way to tune xCode so that it warns you of these types of
potential problems (and more)? The Java development environment
I've been using for the past several years (Jetbrains IDEA) has
unbelievably fantastic code-editing and
20 matches
Mail list logo
