This summs it up really nicely:
http://wbyoung.tumblr.com/post/27851725562/core-data-growing-pains
Links to radar bug reports are within the blog post.
The conclusion it is not usable does not hold under iOS6, since nested contexts
work quite wonderfully there, but it shows problems under
You can use dispatch_sync. The blog post of oliver dobnigg (cocoanetics) summs
that up quite nicely:
http://www.cocoanetics.com/2012/02/threadsafe-lazy-property-initialization/
Cheers, Jörg
On Nov 12, 2012, at 2:44 PM, Tom Davie tom.da...@gmail.com wrote:
On 12 Nov 2012, at 13:39, Marco
, but you can not rely
on it...
Cheers, Jörg
On Nov 12, 2012, at 3:33 PM, Tom Davie tom.da...@gmail.com wrote:
On 12 Nov 2012, at 14:18, Joerg Simon j_si...@mac.com wrote:
You can use dispatch_sync. The blog post of oliver dobnigg (cocoanetics)
summs that up quite nicely:
http
AM, Joerg Simon j_si...@mac.com wrote:
Dear all other Cocoa Developers:
In an app I am developing I have the following strange thing:
[code in the .h file]
@interface XY : CALayer
BOOL _editing;
...
@property (assign, getter = isEditing) BOOL editing;
[/code]
[code in the .m file]
@synthesize
.x iPhone simulator, that
means I can't use the simulator on the iPhone, and it secondly means
that the app has problems to compile with the new compiler, and that
would be bad if apple switches internally.
Any suggestions what to do?
Thanks,
Joerg Simon
