How do I temporary disable warnings in my objective c source file?

Question

One project I work on has a build system that enforces no warnings.

But I have some code that needs warnings to work. Here is an example

NSString* title = @"";
if ([view respondsToSelector:@selector(title)]) {
  title = [view title];
}

After some googling I tried disable warnings for the code block by wrapping that code area with

#pragma warning disable
// my code
#pragma warning restore

Didn't work :(

Anyone know how to do this in Xcode?

Any help is appreciated.

-CV

possible duplicate http://stackoverflow.com/questions/194666/is-there-a-way-to-suppress-warnings-in-xcode — AndersK, Mar 03 '11 at 13:14

Inder Kumar Rathore · Answer 1 · 2014-01-16T07:14:03.213

11

#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wshadow-ivar"
// your code
#pragma GCC diagnostic pop

You can learn about GCC pragma here and to get the warning code of a warning go to the Log Navigator (Command+7), select the topmost build, expand the log (the '=' button on the right), and scroll to the bottom and there your warning code is within square brackets like this [-Wshadow-ivar]

Edit

For clang you can use

#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wshadow-ivar"
// your code
#pragma clang diagnostic pop

edited Jan 16 '14 at 07:14

answered Apr 17 '13 at 14:19

Inder Kumar Rathore

39,458
17
135
184

just searched the same after one and half year and found my answer :) – Inder Kumar Rathore Sep 06 '14 at 12:50
In XCode 9.2 it's Command+9. The '=' on the right has 5 horizontal parallel lines. – Doug Voss Apr 06 '18 at 15:42

score 2 · Answer 2 · answered Mar 03 '11 at 13:18

There are a number of things you could do here, but the simplest would probably to rewrite your code just a tad.

NSString* title = @"";

if ([view respondsToSelector:@selector(title)]) {
  title = [(id)view title];
}

Casting the view variable to id before sending the message should ensure that so long as a method named -title exists anywhere, it'll stay silent.

Another option:

NSString* title = @"";

if ([view respondsToSelector:@selector(title)]) {
  title = [view performSelector:@selector(title)];
}

This is a little different from the above, in that it doesn't require the file to "see" any method named title; but it's a bit more wordy.

Edit: I'm aware that neither of these approaches actually turn of warnings for any amount of time, but rather suppress them.

Suppression, when done correctly, at least, is usually better than simply ignoring.

Thanks, that will work. But my code is actually one example of many warnings my code is causing. The #pragma warning disable is what I'm after — CVertex, Mar 03 '11 at 13:28
@CVertex: No, I'm pretty sure that fixing your warnings is what you are *really* after. — Williham Totland, Mar 03 '11 at 13:43
Best fix your code to not generate the warnings. Everywhere. There's always a way and really, it's worth it. — Nick Moore, Jun 06 '11 at 11:05

score 1 · Answer 3 · edited May 23 '17 at 10:28

1

The closest way to do what you want is to use the GCC diagnostic pragma. See this question for details.

edited May 23 '17 at 10:28

Community

1
1

answered Jun 06 '11 at 11:00

Laurent Etiemble

27,111
5
56
81

How do I temporary disable warnings in my objective c source file?

3 Answers3

Linked