Home > Articles > Programming > C/C++

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

The Future

Apple is traditionally very tight-lipped about future products. For example, the Leopard preview site has very few details on the new features added to Objective-C. In recent years, however, Apple has tried hard to "play nice" with the Free Software community—in particular, by minimizing the divergence of the Apple version of the GCC from the main branch. At any point, however, a number of patches haven’t made it into the main tree. For this reason, Apple has its own branch in the GNU CVS repository.

Since Apple’s GCC development branch is public, it’s possible to poke around in it and see what the Apple developers are up to. This isn’t an endeavor for the faint-hearted; the GCC codebase is not the easiest to understand at the best of times. Wouldn’t it be easier if there were a set of simple example programs showing the new features? Well, I closed my eyes and wished hard, and the magical code pixies delivered this link for the Objective-C test suite in the Apple branch. Every new feature has a simple example program used to test functionality. All you need to do is compile them.

If only life were that simple.

While Apple’s Objective-C compiler is Free Software (due to being a branch of the GNU compiler), Apple’s Objective-C runtime library is not. Not only is it not Free Software—the version required by Objective-C 2.0 isn’t released yet. While it’s possible to compile these programs, some of them won’t link, and most of them won’t work. Still, it’s possible to get an idea of what they do, even without compiling.

Garbage Collection

Pretty much any Objective-C programmer will tell you that the one feature he really misses when using Objective-C is garbage collection. OpenStep uses a retain/release reference-counting mechanism that works most of the time, but is sometimes difficult to use (for example, with data structures containing loops).

Garbage collection in Objective-C isn’t exactly new. Tiger shipped with a compiler supporting garbage collection, and the main GNU trunk has supported the Boehm Garbage Collector for a while. The problem is largely with the standard libraries, which must be modified to support garbage collection.

Objective-C 2.0 adds __strong and __weak type qualifiers for pointers. These qualifiers control whether the compiler should notify the runtime garbage collector of assignments to pointers. A pointer defined at __strong will cause garbage collection events to be generated for all events. The __weak qualifier is redundant in declarations (__weak is the default), but it can be used to suppress the generation of garbage collection events by casting a pointer to a __weak pointer before assignment.

Examples of the use of these features can be found in the objc-gc-*.m test cases.

Loose Protocol Definitions

A protocol is a strict formal definition of an interface to a class. Any class that adopts a protocol must implement it. But sometimes you don’t need all of the methods in an interface. You may want to specify a core set of methods as well as a set of convenience methods that might allow more efficiency, but aren’t absolutely required.

The new @optional and @required keywords permit this flexibility. Any method in a protocol defined as @required behaves like a method in a traditional Objective-C protocol; all classes that adopt the protocol must implement it. @optional methods are advisory; they’re ones that a class can implement, but doesn’t have to. A string class, for example, might be required to provide methods for inserting and removing objects at a specific location, but may also provide a method for replacing a character, which would be more efficient than inserting and deleting as two separate operations.

Examples of the use of these keywords can be found in the enhanced-proto-*.m test cases.

Concrete Protocols

Objective-C, just like Smalltalk, doesn’t have multiple inheritance. This was a design decision, as it was with Java, because multiple inheritance can cause headaches. Instead, Objective-C has categories, which allow methods to be added to an existing class, and protocols that specify interfaces.

Objective-C 2.0 adds the concept of a concrete protocol. Whereas a protocol is a definition of an interface, a concrete protocol adds some implementation detail as well. If the class that adopts the protocol doesn’t provide its own implementation, it will get the default implementation from the protocol.

These features can be combined effectively with @optional methods in a protocol to provide a default implementation of @optional methods, but allow an implementer to replace them with a more useful method.

Method Attributes

A while ago, the GCC added function attributes to C. These are specified using __attribute__ in the function declaration, and provide some extra metadata to the compiler. The uses of function attributes can be divided into two cases:

  • Optimization hints tell the compiler to do things such as pass some parameters in registers, or reuse results when the same function is called with the same arguments.
  • Coding hints are used to generate warnings when a function is invoked.

Most of the optimization hints don’t make sense in the context of Objective-C methods, since they’re invoked via the objc_msgSend function. The coding hints do make sense, however. Objective-C 2.0 adds support for deprecated and unavailable attributes. If a program calls methods marked with either of these descriptions, the compiler will emit a warning suggesting that the method not be used.

Examples of these options can be found in the method-attribute-*.m test cases.


One nice feature of recent versions of Objective-C is key-value coding, which provides an abstracted interface to getting and setting instance variables. Instance variables are accessed via the objectForKey: method, which calls the correct get method, returns the instance variable, or calls a default handler.

Objective-C 2.0 takes this arrangement a step further with properties. Conceptually similar to public instance variables, properties are more clever. The declaration of a property looks like this:

@property int aProperty;

This syntax provides nice encapsulation, since it gives no information about how the property is accessed. In the implementation section, you might have something like this:

@property (ivar = anInstanceVariable, copies, setter = aSetMethod:) int aProperty;

This would (I believe) return a copy of anInstanceVariable when someone tried to read the property, and invoke the aSetMethod method when it was set. Properties are accessed using the following syntax:

anObject.aProperty = 2;

This is a new syntactic addition to Objective-C objects. Instance variables are accessed using ->, since objects are always handled via pointers. However, it’s consistent with the separator used in key-value coding paths.

Note that property names must be distinct from instance variable names, or an error will be generated.

The test cases related to properties are named property-*.m.

For Each

When you want to iterate over the elements in a collection in Objective-C, you typically create an enumerator and use that. Because this is something that’s commonly done, I wrote a macro to reduce the number of copy-and-paste errors:

#define FOREACH(collection,object,type) FOREACHE(collection,object,type,object ## enumerator)
#define FOREACHE(collection,object,type,enumerator)NSEnumerator * enumerator = [collection objectEnumerator];type object;IMP next ## object ## in ## enumerator = [enumerator methodForSelector:@selector(nextObject)];while((object = next ## object ## in ## enumerator(enumerator,@selector(nextObject))))

This works quite well, and gains a little bit of speed by caching the instance method pointer for the nextObject method in the enumerator. To log every string in an array, you would use it as follows:

FOREACH(anArray, string, NSString*)
  NSLog(@"%@", string);

Objective-C 2.0 adds a new for statement construct for doing this. Here’s the equivalent code in Objective-C 2.0:

for(NSString * string in anArray)
  NSLog(@"%@", string);

The most interesting thing about this is that it doesn’t work on any of the standard collections without modification. It depends on the existence of a method with the following signature:

- (unsigned int)countByEnumeratingWithState:(struct __objcFastEnumerationState *)state objects:(id *)items count:(unsigned int)stackcount;

It’s not immediately obvious why Apple chose this path, since the existing enumerator framework allows this functionality without modification to existing code. Inspecting the __objcFastEnumerationState structure doesn’t provide much more insight, so I poked a little deeper. For reference, the code related to handling the for each statement is found in gcc/objc/objc-act.c.

The for each loop invokes this method to get a C array of up to 16 elements at a time. These are returned via items, and the return value of the method contains the number of elements in the array. All quite simple so far—and a significant efficiency increase, since you need only one method call per 16 elements. In the simple case, the following are roughly equivalent:

for(type element in collection)
  //Do Something


type element;
struct __objcFastEnumerationState state = { 0 };
id items[16];
unsigned long limit
while((limit = [collection countByEnumeratingWithState:&state
  for(unsigned int i=0 ; i<limit ; i++)
    element = items[i];
    //Do Something

This is not quite accurate, though. In cases where the data is stored internally in a C array, the object can return a pointer to that array in state.itemsPtr to avoid copying. In other cases, it sets state.itemsPtr to items and copies the requisite pointers into items.

Tantalizing, however, is the fact that the objc_enumerationMutation() is called in cases where subsequent calls to countByEnumeratingWithState:objects:count change the value of the long integer pointed to by state.mutationsPtr. Unfortunately, objc_enumerationMutation() is a runtime library function that doesn’t exist in published versions of the library, so it’s unclear exactly what it does.

  • + Share This
  • 🔖 Save To Your Account

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