Home > Articles > Programming > C/C++

Hands-On Objective-C 2.0: Blocks

This chapter is an introduction to blocks, an Apple-added extension to C, Objective-C 2.0, and C++. You will learn how to define a block, how a block has access to variables in its surrounding context, how to use a block in your own code, and about the somewhat tricky topic of memory management for blocks. The chapter also explores some pitfalls that can befall an unwary user of blocks.
This chapter is from the book

Blocks provide a way to package up some executable code and a context (various variables) as a single entity so they can be handed off for execution at a later time or on a different thread. In other languages, blocks or similar constructs are sometimes called closures or anonymous functions. Blocks are an Apple-supplied extension to C, Objective-C 2.0, and C++. Apple has submitted blocks to the C standards working group as a proposed extension to C. At the time of this writing, blocks are only available on Mac OS X Snow Leopard (v 10.6 and on iOS 4). They are not available on earlier versions of Mac OS X or iPhone iOS.

Handing off a package of work is useful in many situations, but one of the main driving forces behind the adoption of blocks is Apple's new Grand Central Dispatch (GCD) feature. GCD is designed to make concurrency easier to program and more efficient to execute. Essentially, GCD is a thread pool that is managed for you by the operating system. The idea behind GCD is that the operating system has a global view of all the processes running on your Mac, and allocates resources (CPU, GPU, and RAM) as needed to make things run more efficiently. GCD can make better decisions than a user space program can about the number of threads to use and when to schedule them for execution. You use blocks to submit units of work for GCD to execute.

This chapter is an introduction to blocks. You will learn how to define a block, how a block has access to variables in its surrounding context, how to use a block in your own code, and about the somewhat tricky topic of memory management for blocks. The chapter also explores some pitfalls that can befall an unwary user of blocks.

Before looking at blocks in detail, the chapter takes a pair of detours and looks at two earlier ways of packaging up functionality: function pointers and the Foundation class NSInvocation.

Function Pointers

When the compiler encounters a function call, it inserts a jump instruction to the code that performs the function. (A jump instruction causes the program execution to jump to the specified code instead of executing the line of code directly after the jump instruction.) To return, the function executes a jump instruction back to the line of code following the original function call. In a normal function call, the landing point of the jump instruction (and hence the function that is called) is static. It is determined at compile time. But a function call can be made dynamic through the use of a function pointer.

The following line declares myFunctionPtr as a pointer to a function that takes two ints as arguments and returns an int:

int (*myFunctionPtr) (int, int);

Figure 16.1 shows the anatomy of a function pointer.

Figure 16.1

Figure 16.1 The anatomy of a function pointer

The general form of a function pointer is:

   return_type (*name)(list of argument types);

Function pointers are a low point in C syntax. Instead of reading left-to-right or right-to-left, they read from the inside out. More complicated function pointer declarations can quickly turn into puzzles, as you will see in Exercise 16.1.

You can also declare arrays of function pointers. The following line declares fpArray as an array of 10 pointers to functions. Each function takes a single argument, a pointer to a float, and returns void:

void (*fpArray[10])(float*);

A function pointer can point to a function that has another function pointer as an argument or a return value:

void (*(*complicatedFunctionPointer)(void))(void);

complicatedFunctionPointer is a pointer to a function that takes no arguments and returns a pointer to a function that takes no arguments and returns void.

Declarations like the preceding one are ugly, but you can make your code cleaner by hiding the ugliness with a typedef:

typedef void (*(*complicatedFunctionPointer)(void))(void);
complicatedFunctionPointer fp;

Calling a Function with a Function Pointer

The following example shows how to assign a function to a function pointer and how to call the function using the function pointer:

void logInt( int n )
    NSLog("The integer is: %d", n);
void (*myFunctionPtr)(int); // Declare a function pointer

myFunctionPtr = logInt;     // Make it point to logInt
myFunctionPtr( 5 );         // Execute the function through the pointer

To make the function pointer refer to a function, you simply assign it the name of the function. The function must be defined or visible by a forward declaration at the point it is assigned.

To call a function through a function pointer, you simply add the arguments, encased in parentheses, to the function pointer. A function call through a function pointer is just like a normal function call except that you use the name of the function pointer variable instead of the function name, as shown in the previous code snippet.

Using Function Pointers

One of the primary uses of function pointers is for callbacks. Callbacks are used in situations where you have a function or method that is going to do some work for you, but you would like the opportunity to insert your own code somewhere in the process. To do this, you pass the working function or method a pointer to a function containing the code you want executed. At the appropriate time, the working function or method will call your function for you.

For example, NSMutableArray provides the following method for use in custom sorting:

- (void)sortUsingFunction:
           (NSInteger (*)(id, id, void *))compare
                  context:(void *)context

When you invoke sortUsingFunction:context:, the method sorts the contents of the receiver. To perform the sort, sortUsingFunction:context: must examine pairs of array elements and decide how they are ordered. To make these decisions, sortUsingFunction:context: calls the compare function that you passed in by pointer when the method was invoked.

The compare function must look at the two objects it receives and decide (based on whatever criterion you require) whether they are ordered NSOrderedAscending, NSOrderedSame, or NSOrderedDescending.

sortUsingFunction:context: also passes compare the void* pointer that it received as its context argument. This is a pure pass-through; sortUsingFunction:context: doesn't look at or modify context. context may be NULL if compare doesn't require any additional information.

Listing 16.1 sorts an array containing some NSNumber objects. The address of a BOOL is passed in to control the direction of a numerical sort.

Example 16.1. ArraySortWithFunctionPointer.m

#import <Foundation/Foundation.h>

NSInteger numericalSortFn( id obj1, id obj2, void* ascendingFlag )

   int value1 = [obj1 intValue];
   int value2 = [obj2 intValue];
   if ( value1 == value2 ) return NSOrderedSame;
   if ( *(BOOL*) ascendingFlag )
   return ( value1 < value2 ) ?
   NSOrderedAscending : NSOrderedDescending;
   return ( value1 < value2 )
   ? NSOrderedDescending : NSOrderedAscending;


int main (int argc, const char * argv[])
  NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];

  // Put some number NSNumber objects in an array
  NSMutableArray *numberArray = [[NSMutableArray alloc] initWithCapacity: 5];
  [numberArray addObject: [NSNumber numberWithInt: 77]];
  [numberArray addObject: [NSNumber numberWithInt: 59]];
  [numberArray addObject: [NSNumber numberWithInt: 86]];

  [numberArray addObject: [NSNumber numberWithInt: 68]];
  [numberArray addObject: [NSNumber numberWithInt: 51]];

  NSLog( @"Before sort: %@", [numberArray description] );

  // This flag controls the sort direction.
   // Change it to NO to sort in descending order.
   BOOL ascending = YES;

   // Sort the array
   [numberArray sortUsingFunction: numericalSortFn context: &ascending];

  NSLog( @"After sort: %@", [numberArray description] );

  [numberArray release];
  [pool drain];
  return 0;


  • ascendingFlag is passed in as void*. It must be cast as BOOL* before it can be dereferenced to get the BOOL value.
  • The name of a function, in this case numericalSortFn, can serve as a properly typed pointer to that function. Here, it is used as the argument when invoking sortUsingFunction:context: without defining a separate function pointer variable.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020