Re: Suppressing warning
Re: Suppressing warning
- Subject: Re: Suppressing warning
- From: Fred Leboucher <email@hidden>
- Date: Fri, 18 Apr 2008 07:12:35 +0200
In this particular case, it is indeed a nice way to suppress the
warning, but what if the function is looking that way :
int foo()
{
_asm {
// do something complicated...
mov eax, something
}
}
Then my last mov is indeed the return, but gcc doesn't identify it
that way, and putting a return after that would just override my
actual return value...
On Apr 17, 2008, at 10:53 PM, B.J. Buchalter wrote:
On Apr 17, 2008, at 4:50 PM, Jeff LaMarche wrote:
When creating a synchronized accessor, like this (simple example):
- (NSString *)foo
{
@synchronized(foo)
{
return foo;
}
}
You could put a
return NULL;
after the @synchronized
block. It should never be reached...
B.J. Buchalter
Metric Halo
http://www.mhlabs.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40free.fr
This email sent to email@hidden
_______________________________________________
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