RE: "Statement with no effect" warning
RE: "Statement with no effect" warning
- Subject: RE: "Statement with no effect" warning
- From: "Michael Stauffer" <email@hidden>
- Date: Thu, 21 Jun 2007 13:03:55 -0400
- Importance: Normal
Title: Message
|
Thanks
Chris.
I'll try using
__attribute__, that sounds like a good solution.
The code in question
is debug-build-only code that is inconvenient, but probably not impossible, to
remove completely by #ifdef for release builds. I have some macros that evaluate
to nothing in final release builds, and these are giving the "statement has no
effect" and associated warnings.
Cheers,
Michael
On Jun 20, 2007, at 9:27 PM, Michael Stauffer wrote:
Is there a way to suppress the "statement has no effect" and the
"left-hand
operand of comma _expression_ has no effect" warnings? I can't find
these
documented. A old post on this list suggests "-no-undefined" but I
can't
find that documented so am not sure what else it might
do.
I am obligated to say that the way to suppress these warnings is to
correct the source code that is triggering them.
As for the "statement with no effect" warning, it depends on what
specific kind of statement it is. Generally -Wno-unused-value will
suppress this warning without turning off all of the unused (function,
variable, label, parameter, value) warning with -Wno-unused.
You may also find success in adding the gcc construct __attribute__((unused)) before the statement or _expression_ that
is triggering the warning.
Having the code in hand would help me be more specific, of course.
Chris
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden