Home > Articles > Programming > Java

This chapter is from the book

2.9. Overcoming macrophobia

2.9.1. Bad macros

C++ insiders disparage the use of the preprocessor, inherited from C. Java goes further by not supporting a preprocessor in the standard language. Experts, including the designers of both languages, advise against using macros. Stroustrup warns:

  • “The first rule about macros is: Don’t use them if you don’t have to. Almost every macro demonstrates a flaw in the programming language, in the program, or in the programmer.10

What really offends Stroustrup and other experts are these two common uses of macros in traditional C:

  • defining constants:

    #defineNITEMS 32
  • implementing generic pseudo-functions:

    #defineABS(x)((x) >= 0 ? x :-(x))

Both of those macro definitions are handled more flexibly and more reliably by features of C++:

const int NITEMS = 32;
template<class T>
 inline T abs(const T x) {return x >= 0 ? x : -x;}

or Java:

public static final int NITEMS = 32;
public T abs(final T x)//Member of class T
   {return x.greaterThan(0) ? x : x.minus();}

2.9.2. Good macros

The main benefit of macros in any programming language is that they provide a way of capturing and packaging patterns of code. Specifically, macros are able to

  • localize such patterns for ease of future change
  • facilitate compliance with standards for such patterns
  • minimize or eliminate opportunities for error
  • enhance source-code readability

There is no other way in C++ (and no way at all in Java) to capture code patterns that are not functions. Here’s a small, simple example:

#define ACCESSOR(name, rtnType, expr)     rtntyp name() {return expr;}

A programmer defining the Complex class could use that macro in the class definition:

ACCESSOR(realPart, double, rp)
ACCESSOR(imagPart, double, ip)
ACCESSOR(rho,      double, sqrt(rp*rp + ip*ip))
ACCESSOR(theta,    Angle,  atan2(ip/rp))

Since maintenance programmers scanning the source code would immediately spot those functions and understand their purpose, you wouldn’t need any explanatory commentary. But don’t worry—we’re not going to use that sort of low-level macro coding in this book.

2.9.3. Packaging common patterns in elementary numeric classes

Defining a robust, production-quality class can be awfully tedious and error-prone. We need to implement dozens of methods, follow dozens of rules, and avoid dozens of pitfalls.

Preprocessor macros are the only C++ facility that can help. In Chapter 4, we package the additive pattern, and in Chapter 5, we package the point-extent pattern using mainly the simplest of all preprocessor facilities, the #include macro statement. In Chapter 6, we use some ad hoc macros to reduce the repetition of smaller patterns of code, simplifying future program maintenance.

Those simple examples may stir your imagination to consider this approach whenever you find yourself repeating the same pattern of code over and over.

Problems and exercises

2.9-1 Among standard higher-level languages, PL/I provides the most powerful macro (or preprocessor) language. Consult a PL/I manual to learn how macros work, and then try to find some examples that exploit those facilities. Discuss whether a similarly powerful preprocessor would help or hurt program development and maintenance in C++ or Java.


2.9-2 The switch case construct (in Section 2.6.2) works only for integer types. Using macro coding, devise an equivalent flow-control construct switch case that works for any data type. Document any reasonable restrictions due to limitations of the macro language (forbidding nested occurrences of this construct, for example).

2.9.4. #include dependencies

Many #include files, especially class definitions, depend on definitions in other #include files. There are two ways of handling such situations:

  1. The usage documentation for file A can tell the user that file B has to be included first, like this:

    #include B
    #include A
  2. File A can itself contain the preprocessor statement #include B. If file B contains definitions that the compiler should see only once, then it’s customary to surround the code with a multiple-include guard, usually #ifndef . . . . #endif.

The second technique has become common practice among C and C++ programmers, because it localizes knowledge and relieves the programmer of complicated bookkeeping. Nevertheless, there are a few situations in which the first technique is preferable.

One such situation is the packaging of truly global definitions, such as constants, functions, and macros that nearly every program needs and that the programmer should hardly need to think about. Such definitions are like extensions to the C++ language itself.

The online companion to this book, www.dorsethouse.com/books/ooc.html, contains a minimal set of such definitions, file global.hpp. Most organizations will want to expand it to include more conventional names and functions that they wish to be standard for their programming staff or at least for an individual project team—for example, an #include for a string class.

Some experts claim that use of macros impairs program readability by introducing unfamiliar syntax. Experience shows, however, that macros can greatly facilitate readability among groups of programmers who are acquainted with them and use them every day.

This technique also reduces compile times, since global.hpp is opened only once per compile. When programs grow very large, compile times can become surprisingly long; compilers may waste a lot of that time by opening #include files only to skip to the end and close the file because of the multiple-include guard.

Problems and exercises

2.9-3 C programmers often call #include files “header files.” Discuss how that tradition may have originated and whether it’s reasonable today to call every includable source-code file a “header.”

2.9-4 Java’s designers consider a general #include facility unnecessary and potentially dangerous. Consider this view and decide whether you concur. State persuasive reasons to support your position.

2.9-5 A few of the generic functions in global.hpp—such as min(x,y)—duplicate those available in the standard template library (STL). What considerations justify having them in global.hpp?

2.9.5. Macros in this book

In later chapters, we occasionally exploit macros when C++ provides no alternative facility:

  • to capture patterns of code for reuse in multiple components.
  • to “factor out” tedious repetition within a local component to enhance readability and avoid error. The global.hpp example above uses a couple of such local macros.

We refrain, however, from using macros as extensively in this chapter as we do in production code. That way, readers can skip this chapter and still be able to understand every example.

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