Comments on: Objective-C Compiler Warnings http://akosma.com/2009/07/16/objective-c-compiler-warnings/?utm_source=rss&utm_medium=rss&utm_campaign=objective-c-compiler-warnings Leading international provider of cross-platform and multilingual software solutions, for iPhone, iPad, Mac, Windows, Linux, Android, and the web. Tue, 13 Dec 2011 10:51:47 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Migrating iPhone 3.x apps to iPad and iOS 4.0 | akosma softwarehttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-943 Migrating iPhone 3.x apps to iPad and iOS 4.0 | akosma software Mon, 26 Jul 2010 08:44:29 +0000 http://kosmaczewski.net/?p=1633#comment-943 <p>[...] assume your projects compile and link without warnings; many API calls have been deprecated between 2.x and 4.0, so you’d better have code using the [...]</p> [...] assume your projects compile and link without warnings; many API calls have been deprecated between 2.x and 4.0, so you’d better have code using the [...]

]]> By: Craig Mchttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-78 Craig Mc Wed, 26 Aug 2009 08:59:29 +0000 http://kosmaczewski.net/?p=1633#comment-78 <p>CLang is great. I ended up making a simple AppleScript app I could keep in the project folder and double click to fire it up. Nice to hear it's integrated into XCode.</p> <p>I wish we'd used it at my last job - we were forced to use an ancient version of PCLint which did found stuff - oh did it find stuff. You were so busy looking at false positives you'd be lucky to find the real ones. You wouldn't mind so much if the code you were linking against didn't have (literally!) thousands of compiler warnings in it.</p> CLang is great. I ended up making a simple AppleScript app I could keep in the project folder and double click to fire it up. Nice to hear it’s integrated into XCode.

I wish we’d used it at my last job – we were forced to use an ancient version of PCLint which did found stuff – oh did it find stuff. You were so busy looking at false positives you’d be lucky to find the real ones. You wouldn’t mind so much if the code you were linking against didn’t have (literally!) thousands of compiler warnings in it.

]]> By: Adrianhttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-77 Adrian Wed, 26 Aug 2009 08:35:46 +0000 http://kosmaczewski.net/?p=1633#comment-77 <p>heh it's worth it, just because of the integration of the Clang Static Analyzer into it... really good.</p> heh it’s worth it, just because of the integration of the Clang Static Analyzer into it… really good.

]]> By: Craig Mchttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-76 Craig Mc Wed, 26 Aug 2009 08:26:28 +0000 http://kosmaczewski.net/?p=1633#comment-76 <p>Looks like I'm queueing up on Friday then!</p> Looks like I’m queueing up on Friday then!

]]> By: Adrianhttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-75 Adrian Wed, 26 Aug 2009 08:03:06 +0000 http://kosmaczewski.net/?p=1633#comment-75 <p>@Craig shhh, don't tell anyone :) I'm using Xcode 3.2 on Snow Leopard, that might explain why all the options appear.</p> @Craig shhh, don’t tell anyone :) I’m using Xcode 3.2 on Snow Leopard, that might explain why all the options appear.

]]> By: Craig Mchttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-79 Craig Mc Wed, 26 Aug 2009 07:55:44 +0000 http://kosmaczewski.net/?p=1633#comment-79 <p>I'm stumped - how do you get that dialog with all the fabulous warning options?</p> <p>When I open my active target and search there's no group for compiler warnings. I've got an iPhone XCode 3 project targeting SDK 3.0 using gcc4.2. I only have a few paltry user-defined flags GCC_WARN_ABOUT_RETURN_TYPE and GCC_WARN_UNUSED_VARIABLE in the build pane of my target settings. I'd love to get all the options shown above.</p> <p>I've always developed C programs using -Wall and --pedantic and it definitely makes for better software. I'm amazed at how many warnings is in shipped code even from supposedly "quality" shops that imagine they're CMM level 5.</p> I’m stumped – how do you get that dialog with all the fabulous warning options?

When I open my active target and search there’s no group for compiler warnings. I’ve got an iPhone XCode 3 project targeting SDK 3.0 using gcc4.2. I only have a few paltry user-defined flags GCC_WARN_ABOUT_RETURN_TYPE and GCC_WARN_UNUSED_VARIABLE in the build pane of my target settings. I’d love to get all the options shown above.

I’ve always developed C programs using -Wall and –pedantic and it definitely makes for better software. I’m amazed at how many warnings is in shipped code even from supposedly “quality” shops that imagine they’re CMM level 5.

]]> By: links for 2009-07-17 « Blarney Fellowhttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-74 links for 2009-07-17 « Blarney Fellow Sat, 18 Jul 2009 01:08:04 +0000 http://kosmaczewski.net/?p=1633#comment-74 <p>[...] Open Kosmaczewski – Objective-C Compiler Warnings (tags: objective-c viapssteam) [...]</p> [...] Open Kosmaczewski – Objective-C Compiler Warnings (tags: objective-c viapssteam) [...]

]]> By: Adrianhttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-73 Adrian Fri, 17 Jul 2009 07:57:55 +0000 http://kosmaczewski.net/?p=1633#comment-73 <p>@serpah: nooooo!!! OK OK I'll remove them all! Promise :)))</p> @serpah: nooooo!!! OK OK I’ll remove them all! Promise :) ))

]]> By: Adrianhttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-72 Adrian Fri, 17 Jul 2009 07:48:44 +0000 http://kosmaczewski.net/?p=1633#comment-72 <p>Hi everyone! Thanks for all the comments and the "heads-up"! Indeed I updated the post with the reasons why I used to avoid id<SomeProtocol> variables (the reason was the use of "respondsToSelector:"), but I found out that you can declare protocols as conforming to the NSObject protocol (!) and that solves the problem too. So now, instead of "avoiding" using id, it's just another option.</p> Hi everyone! Thanks for all the comments and the “heads-up”! Indeed I updated the post with the reasons why I used to avoid id variables (the reason was the use of “respondsToSelector:”), but I found out that you can declare protocols as conforming to the NSObject protocol (!) and that solves the problem too. So now, instead of “avoiding” using id, it’s just another option.

]]> By: Mikehttp://akosma.com/2009/07/16/objective-c-compiler-warnings/comment-page-1/#comment-71 Mike Fri, 17 Jul 2009 07:40:56 +0000 http://kosmaczewski.net/?p=1633#comment-71 <p>Seems I made the same mistake as Ryan and forgot to escape the angle-brackets in my second id; id<SomeProtocol>.</p> Seems I made the same mistake as Ryan and forgot to escape the angle-brackets in my second id; id<SomeProtocol>.

]]>