#automatic-ref-counting

Solution: Custom dealloc and ARC (Objective-C) #computers #development #answer

Custom dealloc and ARC (Objective-C)

In my little iPad app I have a “switch language” function that uses an observer. Every view controller registers itself with my observer during its viewDidLoad:.

- (void)viewDidLoad { [super viewDidLoad]; [observer registerObject:self]; }

When the user hits the “change language” button, the new language is stored in my model and the observer is notified and…

Resolved: Override setter with arc #fix #dev #solution

Override setter with arc

@interface Article : NSObject @property (nonatomic, strong) NSString *imageURLString; @end @implementation Class @synthesize imageURLString = _imageURLString; - (void)setImageURLString:(NSString *)imageURLString { _imageURLString = imageURLString; //do something else }

Did I correctly override the setter when ARC is enabled?

Answer [by Pascal]: Override setter with arc

Y…

Fixed How do I avoid capturing self in blocks when implementing an API? #dev #it #asnwer

How do I avoid capturing self in blocks when implementing an API?

I have a working app and I’m working on converting it to ARC in Xcode 4.2. One of the pre-check warnings involves capturing selfstrongly in a block leading to a retain cycle. I’ve made a simple code sample to illustrate the issue. I believe I understand what this means but I’m not sure the “correct” or recommended way to implement…

Fixed Disable Automatic Reference Counting for Some Files #dev #it #asnwer

Disable Automatic Reference Counting for Some Files

I have downloaded the iOS 5 SDK and found that ARC is a great feature of the new Apple compiler. For the time being, many third party frameworks don’t support ARC. Could I use ARC for my new code and keep the current retain/release code unchanged? The ARC converter doesn’t work here, because some frameworks, such as JSONKit, cannot be converted…

How to: Objective-C: Why is autorelease (@autoreleasepool) still needed with ARC?

Objective-C: Why is autorelease (@autoreleasepool) still needed with ARC?

For the most part with ARC (Automatic Reference Counting), we don’t need to think about memory management at all with Objective-C objects. It is not permitted to create NSAutoreleasePools anymore, however there is a new syntax:

@autoreleasepool { … }

My question is, why would I ever need this when I’m not supposed to be…

Fixed What kind of leaks does automatic reference counting in Objective-C not prevent or minimize? #dev #it #asnwer

What kind of leaks does automatic reference counting in Objective-C not prevent or minimize?

In the Mac and iOS platforms, memory leaks are often caused by unreleased pointers. Traditionally, it has always been of utmost importance to check your allocs, copies and retains to make sure each has a corresponding release message.

The toolchain that comes with Xcode 4.2 introduces automatic reference…

Fixed Why does Apple recommend to use dispatch_once for implementing the singleton pattern under ARC? #dev #it #asnwer

Why does Apple recommend to use dispatch_once for implementing the singleton pattern under ARC?

What’s the exact reason for using dispatch_once in the shared instance accessor of a singleton under ARC?

+ (MyClass *)sharedInstance { // Static local predicate must be initialized to 0 static MyClass *sharedInstance = nil; static dispatch_once_t onceToken = 0; dispatch_once(&onceToken, ^{…

Fixed Objective-C declared @property attributes (nonatomic, copy, strong, weak) #dev #it #asnwer

Objective-C declared @property attributes (nonatomic, copy, strong, weak)

Can someone explain to me in detail when I must use each attribute: nonatomic, copy, strong, weak, and so on, for a declared property, and explain what each does? Some sort of example would be great also. I am using ARC.

Answer: Objective-C declared @property attributes (nonatomic, copy, strong, weak)

This link has the…