automatic-ref-counting

I maintain a dispatch queue as a property with my view controller. I create this queue once in my view controller's init method, and reuse a few times for some background tasks. Before ARC, I was doing this: @property (nonatomic, assign) dispatch_queue_t filterMainQueue; And in init: if (filterMainQueue == nil) { filterMainQueue = dispatch_queue_create("com.myQueue.CJFilterMainQueue", NULL); } But after ARC, I'm not sure if this should still be "assign", or should it be "strong" or "weak". The ARC convertor script didn't change anything but I'm not sure if a subtle bug is coming from the fact

My question is the following: I have a singleton type object (I'm using ARC) that has this code in the implementation file +(id)sharedInstance { static DataManager *sharedInstance; if (sharedInstance == nil) { sharedInstance = [[DataManager alloc] init]; } return sharedInstance; } +(NSManagedObjectContext *)getManagedContext { AppDelegate *applicationDelegate =(AppDelegate *)[[UIApplication sharedApplication] delegate]; return [applicationDelegate managedObjectContext]; } +(void)saveContext:(NSManagedObjectContext *)context { NSError *error; if (![context save:&error]) { NSLog(@"Whoops, couldn

What are the advantages and disadvantages of using the new automatic reference counting (ARC) memory management style in an iOS project? Can you choose not to use ARC when developing with the iOS 5.0 SDK? Do you recommend ARC or manual reference counting (MRC) for a new project? Will an application using ARC be able to run on older OS versions than iOS 5.0? justin What are the advantages and disadvantages of using the new automatic reference counting (ARC) memory management style in an iOS project? An ARC program's execution is nearly identical to well written MRC. That is, the behavioral

I have a category class for NSString. @implementation NSString (URLEncode) - (NSString *)URLEncodedString { __autoreleasing NSString *encodedString; NSString *originalString = (NSString *)self; encodedString = (__bridge_transfer NSString * ) CFURLCreateStringByAddingPercentEscapes(NULL, (__bridge CFStringRef)originalString, NULL, (CFStringRef)@"!*'();:@&=+$,/?%#[]", kCFStringEncodingUTF8); return encodedString; } Am I using the correct bridge transfers for ARC and the new LLVM? The original code: - (NSString *)URLEncodedString NSString *encodedString = (NSString *

I did work several times with blocks as with pointers to which i had strong reference I heard that you should use copy, but what is the implication in working with blocks as pointers and not with the raw object? I never got a complain from the compiler, that i should not use @property (nonatomic, strong) MyBlock block; but should use @property (nonatomic, copy) MyBlock block; as far as i know, the block is just an object, so why to preferrer copy anyway? CRD Short Answer The answer is it is historical, you are completely correct that in current ARC code there is no need to use copy and a

I assure you that I did look for an answer in SO for my question but none of them were helpful. Here I got a simple code that should present a UIImagePickerController within a UIPopoverController : -(void)takePicture:(id)sender{ UIImagePickerController *picker=[[UIImagePickerController alloc] init]; picker.delegate=self; picker.sourceType=UIImagePickerControllerSourceTypeCamera; picker.allowsEditing=YES; UIPopoverController *poc=[[UIPopoverController alloc] initWithContentViewController:picker]; [poc presentPopoverFromBarButtonItem:bbItem permittedArrowDirections:UIPopoverArrowDirectionAny