Home > Articles > Programming > C/C++

Looking Forward to Objective-C Literals

Ready for the next generation of Objective-C improvements? Get ready for enhanced literals! These new features simplify your code and improve readability. In this write-up, you'll discover what these literals are, how you use them, and why they'll help your day-to-day development — bestselling author Erica Sadun introduces all the basics you need to get started. Read on to explore these features and preview the power the next generations of Xcode will introduce.
Like this article? We recommend

In all likelihood, OS X 10.8 Mountain Lion's debut remains months away. During Apple's Q2 financials conference call, company spokespersons said the upgrade would ship "late Summer" 2012. Many people are looking forward to Mountain Lion's new iOS-inspired features such as reminders and notification center. Developers, however, are promised a new set of tools currently being previewed in the Xcode 4.5 beta release.

Normally, features in a beta toolset are out of bounds due to non-disclosure agreements (NDAs). With apologies to Chuck Palahniuk, the first rule of NDA is "You don't talk about NDA material." The second rule of NDA is "You don't talk about NDA material," and so forth.

With Xcode's LLVM/clang, Apple regularly pushes documentation and source to the public llvm.org website, excluding these new features from NDA considerations. This March, Apple added an update talking about an exciting new set of Objective-C features for the clang compiler. These new Objective-C Literals introduce new ways to simplify object creation in code.

This write-up introduces some of these new features and discusses how you'll be able to use them in your code using the new compiler.

New Literals

Detailed at LLVM's website, new Objective-C literals introduce features that transform awkward constructs like NSNumber and NSArray creation instances into parsimonious expressions.

Think about how often you type cookie-cutter templates like [NSNumber numberWithInteger:5] to produce number objects in your code. Perhaps you've defined macros to simplify your coding. Speaking as someone who has long created macro definitions for the NSNumber declarations, I look forward to the way these literals provide more readable, succinct code. They save an enormous amount of typing and provide a natural, coherent presentation.

Now, instead of establishing endless series of those declarations, consider using a simple literal like @5. This number literal is just like the strings literals you've used for years. With strings, the at-sign followed by a string constant, e.g. @"hello". Clang 3.1 introduces the same kind of literal declaration to numbers and collections, an at-signed followed by a number value.

This new advance squeezes together previously wordy constructs to create simpler, more succinct representations.


Clang's new number literals allow you to wrap scalar values like integers and floating point numbers into object containers. Just add a @-prefix to a scalar. For example, you can transform 3.1415926535 to a conforming NSNumber object as follows:

NSNumber *eDouble = @ 2.7182818;

This number literal is functionally equivalent to the following.

NSNumber *eDouble = [NSNumber numberWithDouble: 2.7182818];

The difference is that the compiler takes care of the heavy lifting for you. You don't have to use a class call and you don't have to write out a full method, brackets and all. Instead, you prefix the number with an @-sign and let clang do the rest of the work.

Standard suffixes allow you to specify whether a number is a float (F), long (L), longlong (LL), or unsigned (U). Here are some examples of how you would do that. Notice how simple each declaration is, without having to use numerous specialized method calls.

NSNumber *two = @2;                 // [NSNumber numberWithInt:2];
NSNumber *twoUnsigned = @2U;        // [NSNumber numberWithUnsignedInt:2U];
NSNumber *twoLong = @2L;            // [NSNumber numberWithLong:2L];
NSNumber *twoLongLong = @2LL;       // [NSNumber numberWithLongLong:2LL];
NSNumber *eDouble = @2.7182818;     // [NSNumber numberWithDouble: 2.7182818];
NSNumber *eFloat = @2.7182818F;     // [NSNumber numberWithFloat: 2.7182818F];

Unfortunately you cannot wrap long double numbers according to the clang specification. Be aware that the follow statement will cause the compiler to complain. (Apple's runtime doesn't support long doubles either.)

NSNumber *eLongDouble = @2.7182818L // Will not compile


Clang 3.1 supports only literal scalar constants after the @-sign. If you want to interpret a value and then convert it to a number object, you have to use the traditional method call:

NSNumber *two = [NSNumber numberWithInt:(1+1)];

Boxed expressions, i.e. values that are interpreted and then converted to number objects, will debut in clang 3.2. A boxed expression is enclosed in parentheses, telling the compiler to evaluate and then convert to an object e.g.

NSNumber *two = @(1+1);

int foo = ...; // some value
NSNumber *another = @(foo);

While 3.2-compliant, this boxed expression is not supported in clang 3.1. So you must exercise care when using constants like INT_MIN and INT_MAX. As the clang-site documentation points out, these items are defined as follows:

#define INT_MAX   2147483647  /* max value for an int */
#define INT_MIN   (-2147483647-1) /* min value for an int */

Notice how INT_MAX refers to a plain literal, while INT_MIN is evaluated as an expression. @INT_MAX works in clang 3.1 but @INT_MIN will not work until clang 3.2.

There are other considerations to think about as full support for boxing rolls out. Take enums for example. While you'd think you should be able to define an enum and then use them directly, allowing user-defined sequences that start with an @ and continue with text could cause issues. Observe the following poorly chosen enum:

enum {interface, implementation, protocol};

You might imagine you could create an NSNumber with the value 2 by defining:

NSNumber *which = @protocol;

That would, quite obviously, be bad. Boxing prevents any conflict with current and future @-delimited literals:

NSNumber *which = @(protocol); // [NSNumber  numberWithInt:2];

The boolean @YES and @NO, which produce number objects equivalent to [NSNumber numberWithBool:YES] and [NSNumber numberWithBool:NO] should be in a compliant 3.1 release. A caution: check for actual support in the compiler you use. Details follow later in this write-up.

Boxed expressions are not limited to numbers. They work for strings as well. The following assignment evaluates the results of strstr and forms an NSString from the results (i.e. @"World!").

NSString *results = @(strstr("Hello World!",  "W"));

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