This seems, to me, to be a bug in the compiler (I can easily reproduce
it on the desktop). Please file a report at
http://bugreport.apple.com.
Yep, it's a bug all right. A report has been filed.
Loren
___
Cocoa-dev mailing list
Yes,
at this line:
NSString *n = [o someMethod].someProperty;
the -someMethod method body is literally executed twice (control isn't
handed back to the calling function until after the second return
self;.
- (MyTestClass *)someMethod
{
NSLog(@someMethod called);
return self;
}
Perhaps I'm blind, but after pouring over every scrap of information I
could find, I could not find the answer to this question.
Are -retain and -release thread-safe? (Perhaps as atomic increments/
decrements internally?)
___
Cocoa-dev mailing
, atebits wrote:
Perhaps I'm blind, but after pouring over every scrap of
information I
could find, I could not find the answer to this question.
Are -retain and -release thread-safe? (Perhaps as atomic
increments/decrements internally?)
Yes, -retain and -release are thread-safe. It's