4. Object Creation and Storage | Objective C Memory Management Essentials

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Objective C Memory Management Essentials

By : Tang

3.3 (3)

Objective C Memory Management Essentials

3.3 (3)

By: Tang

Overview of this book

If you are new to Objective-C or a veteran in iOS application development, this is the book for you. This book will ensure that you can actively learn the methods and concepts in relation to memory management in a more engaging way. Basic knowledge of iOS development is required for this book.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Introduction to Objective-C Memory Management

1. Introduction to Objective-C Memory Management

Why do we need memory management in Objective-C?

An object's ownership and life cycle

Ownership of object and reference counting

What's a memory leak and why pay attention to it?

What is an object within Objective-C?

Summary

2. Automatic Reference Counting

2. Automatic Reference Counting

What is ARC and how does it work?

How ARC looks

Project settings for ARC

A memory model in Objective-C

What you need to know about ARC and weak references

Summary

3. Using Autorelease Pools

3. Using Autorelease Pools

Understanding the autorelease pool mechanism

Autorelease pool mechanism

An overview of Apple autoreleased classes

ARC and autorelease

Autorelease pool blocks and threads

Summary

4. Object Creation and Storage

4. Object Creation and Storage

Creation and initialization of objects

What is a class?

Object immutability

Object mutability

Inheritance

Convenience initializers

An Objective-C programmer's responsibility

The singleton pattern

Creating @property

Creating custom methods

String formatting

Summary

5. Managing Your Application Data

5. Managing Your Application Data

Device memory

Caching

SQLite

Summary

6. Using Core Data for Persistence

6. Using Core Data for Persistence

Why use Core Data?

Understanding Core Data concepts

Putting it into practice

Getting into the code

Saving data into the persistent store

Deleting data from the persistent store

Updating data

Summary

7. Key-value Programming Approaches

7. Key-value Programming Approaches

What is key-value coding or KVC?

The NSKeyValueCoding protocol

Manual subsets of NSKeyValueCoding behavior

Associated objects

Selectors as keys

Maximum flexibility and handling unusual keys/values

Key-value observing

Summary

8. Introduction to Swift

8. Introduction to Swift

Welcome to Swift

Basics of Swift

Memory management in Swift

Summary

9. Memory Management and Debugging

9. Memory Management and Debugging

Memory leaks

Using the debugger and breakpoints

Collecting data on your app

Plumbing memory leaks

Using the LLVM / Clang Static Analyzer

Summary

10. Tips and Tricks for Memory Management

10. Tips and Tricks for Memory Management

Objective-C, C, and memory management

Getters and setters

The property attribute in Objective-C

Performance guidelines

Don't overthink about memory management

When to avoid KVC and KVO

Summary

11. Features of Xcode 6

11. Features of Xcode 6

Introducing Xcode 6

What's new in storyboard

Debugging in Xcode 6

What's new in Interface Builder

Playground for Swift

Summary

Index

Index

Customer Reviews

3.3 (3)

5 star

33.3%

4 star

0

3 star

33.3%

2 star

33.3%

1 star

0

An Objective-C programmer's responsibility

If you have experience in other programming languages, such as Java, and are coming to Objective-C now, forget about constructors, they don't exist in Objective-C. Constructors are language-level constructs that merge the allocation and initialization actions, but they have restrictions:

They don't return anything. While the Objective-C class initialization method, + (void) initialize, does not return anything, the default—(id) init method of an Objective-C class returns an object of the type id.
The constructor's name must be identical with the class.
When you call the superclass, being the first statement is a must.

The last point ensures you won't deal with garbage data, but this is a restriction. In Objective-C, as in C, without this restriction, you, the programmer, have more flexibility and power, but it is also your responsibility to deal with garbage data.

Search

Your notes and bookmarks