Comments on: Objective-C Compiler Warnings

By: Migrating iPhone 3.x apps to iPad and iOS 4.0 | akosma software

Migrating iPhone 3.x apps to iPad and iOS 4.0 | akosma software — Mon, 26 Jul 2010 08:44:29 +0000

[...] 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 Mc

Craig Mc — Wed, 26 Aug 2009 08:59:29 +0000

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: Adrian

Adrian — Wed, 26 Aug 2009 08:35:46 +0000

heh it’s worth it, just because of the integration of the Clang Static Analyzer into it… really good.

By: Craig Mc

Craig Mc — Wed, 26 Aug 2009 08:26:28 +0000

Looks like I’m queueing up on Friday then!

By: Adrian

Adrian — Wed, 26 Aug 2009 08:03:06 +0000

@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 Mc

Craig Mc — Wed, 26 Aug 2009 07:55:44 +0000

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 Fellow

links for 2009-07-17 « Blarney Fellow — Sat, 18 Jul 2009 01:08:04 +0000

[...] Open Kosmaczewski – Objective-C Compiler Warnings (tags: objective-c viapssteam) [...]

By: Adrian

Adrian — Fri, 17 Jul 2009 07:57:55 +0000

@serpah: nooooo!!! OK OK I’ll remove them all! Promise ))

By: Adrian

Adrian — Fri, 17 Jul 2009 07:48:44 +0000

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: Mike

Mike — Fri, 17 Jul 2009 07:40:56 +0000

Seems I made the same mistake as Ryan and forgot to escape the angle-brackets in my second id; id.