Home > Store

Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference

Register your product to gain access to bonus material or receive a coupon.

Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference


  • This product currently is not for sale.
Not for Sale


  • Copyright 2000
  • Dimensions: 7-3/8x9-1/4
  • Pages: 672
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-18395-1
  • ISBN-13: 978-0-201-18395-5

IOStreams and Locales are two of the most important, eagerly-awaited components of the ISO/ANSI C++ standard -- and this is the first book to cover them exclusively, and in great depth. The authors explain the problems that IOStreams and Locales solve; then present a wide range of examples and techniques, from simple to sophisticated. The authors introduce concepts, component architecture, standards-compliant code, and practical patterns of use. Coverage includes: key differences between standard IOStreams and the non-standard versions that preceded it; how to extend the Locales component for more effective internationalization; and more. The book also includes a complete, authoritative class reference. Experienced developers can use the book as a start-to-finish learning tool, or as a handy "just-in-time" reference for specific techniques.


Author's Site

Untitled Document Visit the author's web site to get additional book information, including errata and code.

Sample Content

Table of Contents



Guide to Readers.


1. IOStreams Basics.

Input and Output.

Formatted Input/Output.

The Predefined Global Streams.

The Input and Output Operators.

The Format Parameters of a Stream.


The Locale of a Stream.

Comparison Between Formatted Input and Output.

Peculiarities of Formatted Input.

The Stream State.

The Stream State Flags.

Checking the Stream State.

Catching Stream Exceptions.

Resetting the Stream State.

File Input/Output.

Creating, Opening, Closing and Destroying File Streams.

The Open Modes.

Bidirectional File Streams.

In-Memory Input/Output.

Unformatted Input/Output.

Stream Positioning.

Synchronization of Streams.

Means of Synchronization.

Synchronization via flush() and sync().

Synchronization using the unitbuf Format Flag.

Synchronization by Tying Streams.

Synchronizing the Predefined Standard Streams.

Synchronization Among the Predefined Standard Streams.

Synchronization with the C Standard I/O.

Synchronization with the External Device.

Synchronization Between Predefined Standard for Narrow and Wide Characters.

2. The Architecture of IOStreams.

The Stream Class.

Class Heirarchy.

The Stream Base Classes.

The General Stream Classes.

The Concrete Stream Classes.

How Streams Maintain their Stream Buffer.

Copying and Assignment of Streams.

How Streams Maintain Their Locale.

Collaboration Among Streams, Stream Buffers, and Locales.

The Stream Buffer Classes.

Class Heirarchy.

The Stream Buffer Abstraction.

String Stream Buffers.

File Stream Buffers.

Character Types and Character Traits.

Character Representations.

Character Traits.

Requirements of a Character Traits Type.

The End-of-File Character.

Copying, Finding, and Comparing Characters.

Conversion State.

Stream Positions.

The Predefined Standard Character Traits.

Character Types.

Requirements for Character Types.

Stream Iterators and Stream Buffer Iterators.

The Concepts of Iterators in the Standard Library.

Stream Iterators.

Output Stream Iterator.

Input Stream Iterator.

Stream Iterators are One-Pass Iterators.

Stream Buffer Iterators.

Output Stream Buffer Iterator.

Input Stream Buffer Iterator.

Additional Stream Storage and Stream Callbacks.

Additional Stream Storage.

Stream Callbacks.

3. Advanced IOStreams Usage.

Input and Output of User-Defined Types.

The Signature of Inserters and Extractors.

First Inserters and Extractors.


Format Control.

Prefix and Suffix Operations.

Error Indication.


I/O Operations.

Refined Inserters and Extractors.


Prefix and Suffix Operations.

Format Control.

Error Indication.

Using the Refined Inserter and Extractor.

Generic Inserters and Extractors.

Simple Versus Refined Approach.

User-Defined Manipulators.

Manipulators Without Parameters.

Manipulators with Parameters.

Straightforward Manipulator Implementations.

Generalized Technique: Using a Manipulator Base Template.

Variants of a Manipulator Implementation.


Manipulator Base Template with Error Handling.

Manipulators with State.

The Standard Manipulator Base Type smanip.

Extending Stream Functionality.

Using Stream Storage for Private Use: iword, pword, and xalloc.

Initializing and Maintaining the iword/pword Index.

Implementing the Date Inserter.

Implementing the Maniuplator.

Using Stream Callbacks for Memory Management.

Error Indication of Stream Callback Functions.

Extending the Example.

Using the New Functionality.

Evaluation of the iword/pword Approach.

Creating New Stream Classes by Derivation.

Deriving the New Stream Classes by Derivation.

Implementing the Date Inserter and the Manipulator.

Implementing the Date Inserter.

Implementing the Manipulator.

Using the New Functionality.


Comparing Both Solutions—iword/pword Versus Derivation.

Adding Stream Buffer Functionality.

Deriving from the Stream Buffer Base Class.

Core Functionality of Stream Buffers Character Transportation.

Stream Buffer for Unbuffered Character Transport.

Stream Buffer for Buffered Character Transport.

Optional Functionality of Stream Buffers.

Providing New Stream Classes Along with New Stream Buffer Classes.

Deriving from Concrete Stream Buffer Classes.


4. Introduction to Internationalization and Localization.

Internationalization and Localization.

Cultural Conventions.


Numerical Values.

Monetary Values.

Time and Date.

Sorting Words.


Character Encodings.

Terms and Definitions.

Character Codesets.

Character Encoding Schemes.

Japanese Multibyte Encoding Schemes.

Uses of Multibyte Encodings and Wide Characters.

Code Conversions.

5. Locales.

Creating Locale Objects.

Named Locales.

Combined Locales.

The Global Locale.

Retrieving Facets from a Locale.



6. Standard Facets.

Alphabet- and Language-Related Facets.

Character Classification.

Character Classification.

Character Conversion to Upper- and Lowercase.

Character Conversion Between charT and char.

Special Properties of ctype<char>.

String Collation.

Code Conversion.

Message Catalogs.

Formatting and Parsing Facets.

Numerical and Boolean Values.

The numpunct Facet.

The num_put Facet.

The num_get Facet.

Monetary Values.

The moneypunct Facet.

The money_put Facet.

The money_get Facet.

Date and Time Values.

The time_put Facet.

The time_get Facet.

Grouping of Standard Facets in a Locale.

The Standard Facet Families.

The Standard Facet Base Class Templates.

The Derived by name Facets.

Behavior of the Base Class Facets.

Mandatory Facet Types.

Locale Categories.

Diagram: Facets and Categories.

Advanced Usage of the Standard Facets.

Indirect Use of a Facet Through a Stream.

Use of a Facet Through a Locale.

Direct Use of the Facet Independent of a Locale.

7. The Archtecture of the Locale Framework.

Class Hierarchy.

Identification and Lookup of Facets in a Locale.

Facet Identification.

Facet Lookup.

Retrieval of Facets from a Locale.

Storing Facets in a Locale.

The Rationale Behind the Use of the Two-Phase Polymorphism.

Memory Management of Facets in Locale.

The Facet Reference Counter.

Immutability of Facets in a Locale.

8. User-Defined Facets.

Adding a User-Defined Facet to an Existing Facet Family.

Defining a New Facet Family.

Reference Guide.
1. Locale.

header file.

global functions.






























2. Character Traits.

header file<string>.




3. IOStreams.

header file<iosfwd>.

global type definitions.

global objects.

















4. Stream Iterators.

header file<iterator>.




iterator category tags.



5. Other I/O Operations.

bitset .



Appendix A: Parsing and Extraction of Numerical and bool Values.

A.1 Parsing Numerical Values.

A.2 Parsing bool Values.

A.3 Conversion Specifier and Length Modifier.

Appendix B: Formatting of Numerical and bool Values.

B.1 Formatting Numerical Values.

B.2 Formatting bool Values.

B.3 Conversion Specifiers, Qualifiers, and Length Modifiers.

Appendix C: strftime() Conversion Specifiers.
Appendix D: Correspondences Between C and C++IOStreams.

D.1 File Open Modes.

D.2 Stream Positions.

Appendix E: Differences Between Classic and Standard IOStreams.

E.1 Templatizing the IOStreams Classes.

E.2 Splitting Base Class ios.

E.3 Indicating Errors.

E.4 Internationalizing IOStreams.

E.5 Removing_withassign Classes.

E.6 Removing File Descriptors.

E.7 String Streams: Replacing strstream by stringstream.

E.8 Changes to the Stream Buffer Classes.

E.9 Minor changes.

Appendix F: Relationship Between C and C++ Locales.

F.1 Locale Categories in C and C++.

F.2 The Global Locale in C and C++.

Appendix G: New C++ Features and Idoms.

G.1 Bitmask Types.

G.2 POD--Plain Old Data.

G.3 Explicit Constructors.

G.4 Template Specialization.

G.5 Default Template Arguments.

G.6 Explicit Template Argument Specification.

G.7 The Typename Keyword.

G.8 Dynamic Cast.

G.9 Function try Blocks.

G.10 Standard Exceptions.

G.11 Numeric Limits.

G.12 C++ Strings.

Index. 0201183951T04062001


Since 1998, the programming language C++ has been formerly specified in the form of the ISO/IEC International Standard 14882, a document that for historical reasons is often referred to as the ANSI C++ Standard. Integral to this standard is a rich set of abstractions known as the C++ Standard Library. In fact, half of the standard is devoted to the library. This book covers two major domains of the standard library: IOStreams and locales.

During the process of standardization from 1989 to 1998, the new language features and the standard library created a fair amount of interest in the C++ community. To address this need for the information, several books were published during and after standardization. Some cover standard C++ in general, typically including a brief introduction to some of the library abstractions; one textbook is devoted exclusively to the standard library. However, the only part of the library that has been discussed in depth so far is the STL, a set of collections and algorithms that was developed at Hewlett-Packard independent of the standardization effort and was later integrated into C++ standard library. While the STL is, without doubt, the most popular part of the standard library, it represents less than a third of the library as a whole (counting the pages in the standards document and considering the time that the committee spent on it), whereas IOStreams and locales form another third of the library.

When we got involved with the standardization of C++ through our professional occupations in 1993, hardly anything had been published about IOStreams, and C++ locales had not yet been invented. The only book on IOStreams was the C++ IOStreams Handbook by Steve Teale, which describes the classic, prestandard IOStreams; and there was a definite lack of information regarding the standardized IOStreams. The situation has not radically changed since then. Even now, at the time of this writing in 1999, little has been published about the standardized IOStreams, and even less about C++ locales. The few books that exist about IOStreams are out of date; they all cover the classic, pre-standard IOStreams. The C++ textbooks provide introductory information about IOStreams but rarely anything about locales. For this reason, we felt the need for a book exclusively devoted to these topics that begins where the tutorials leave off.


This book is a programmer's guide to the standard IOStreams and locales, together with a complete reference of all relevant classes, functions, templates, headers, etc. It is neither a tutorial nor a textbook. It does not aim to teach the reader C++ or the basics of IOStreams. We expect of the readers that they know, at least roughly, what happens when they type a line of C++ code such as

cout << "Hello" << endl;

Hence this book is not for absolute beginners, but rather for C++ programmers who have been studying a C++ textbook, or have comparable practical experience, and who intend to use IOStreams and locales in more than a casual way.

As locales are an abstraction that is new to C++, as opposed to IOStreams, which has been around for more than a decade, we cover locales from the ground up. Some knowledge of locales in C will aid understanding, but it is not required. We do not aim to cover internationalization in a comprehensive way. Internationalization is too broad a topic, and an adequate discussion of it would fill another whole book. However, IOStreams and locales are closely related, and for this reason the book explains the concept of C++ locales, with emphases on usage of locales in conjunction with IOStreams.

Regarding IOStreams, we acknowledge the fact that the classic IOStreams library has been in existence since the early days of C++. We assume that readers are familiar with the basic features as they are explained in every C++ textbook. Instead of repeating the basics, we aim to go beyond that introductory level. For instance, we demonstrate advanced features--such as user-defined shift operators and manipulators, extending streams by use of iword/pword, and derivation of new stream and stream buffer classes--as well as less ambitious topics like format control and error handling.

Overall, the goal of this book is to provide as much information about the general principles as is needed to enable readers to accomplish their concrete programming tasks using IOStreams and locales. The focus is on the underlying concepts and the more advanced programming techniques that IOStreams and locales support, rather than on the details of each and every interface. For this reason we refrain from presenting extensive and lengthy case studies and code examples. IOStreams and locales are general purpose tools and can be used to solve a sheer abundance of problems. It would have been impossible to find a representative and comprehensive set of case studies. Instead, we concentrate on a few condensed examples that we use to explain programming techniques and concepts, and we deliberately refrain from blowing them up to full applications in order to avoid unnecessary distractions. We trust that readers will be astute enough to figure out concrete applications once the principles are clear.


We have received a considerable number of queries such as, "Why is this and that so and so?" seeking an explanation of why IOStreams and locales are designed the way they are. Where we know of an underlying rationale, we explain it. Yet there are inconsistencies and "interesting" design decisions that can be explained only by "historical reasons" or "design by committee." Where we feel that certain features introduce potential pitfalls, we point them out, so that the reader can avoid them. Beyond that, we neither aim to defend the standard nor intend to discuss alternative designs. We describe it as it is.


Writing this book took us more than three years, and during this long period many people helped us to endure and finish the task. As with any book, the authors are only part of the story, and we would like to thank all those people who contributed in one way or another.

At Addison-Wesley, we would like to thank Mike Hendrickson, Deborah Lafferty, and in particular Marina Lang; they believed in the value of this book and accompanied us through the entire process from proposal to print.

We would like to thank all those knowledgeable and patient people at the standards committee and elsewhere who answered our countless and sometimes stupid questions: Nathan Myers, who invented the C++ locales and proposed them to the standards com-mittee, told us everything about locales and helped us understand his proposal as well as any resulting discussions. Jerry Schwarz, who is the "father of IOStreams," that is, the author of the first version of IOStreams (or "streams" as they were called in C++ 1.0), gave us invaluable insights into the intent of many of the IOStreams features, and we thank him for his patience and support. Bill Plauger, author of the Microsoft version of the C++ standard library, helped us find bugs in the implementation resulting from misunder-standings on our side; he was also invaluable in helping us understand and interpret the standard correctly. Philippe LeMouel, a former colleague at RogueWaveSoftware, imple-mented IOStreams there and explained his implementation to us. Joe Delaney worked on RogueWave's implementation of locales. Dietmar Kuehl, worked on the implementation of IOStreams and locales for the gnu compiler. John Spicer of EdisonDesignGroup and Erwin Unruh of Siemens answered questions regarding templates and other language features. Beman Dawes, who maintains the library issue list for the standards committee helped clarify countless open issues in the standard.

Thanks also to our reviewers, some of whom spent a considerable amount of effort and time compiling thorough and helpful comments: (in alphabetical order) Chuck Allison, Stephen Clamage, Mary Dageforde, Amelia Lewis, Stan Lippman, Dietmar Kuehl, Werner Mossner, and Patrick Thompson, as well as others who preferred to stay anonymous.

--Angelika Langer
--Klaus Kreft

I would like to thank Bernd Eggink, author of a book about the classic IOStreams written in German. Our email correspondence about IOStreams spawned the idea of a joint book project on the standard IOStreams. The original idea had been to translate his book into English and upgrade to the standard, but his sudden, serious illness thwarted our plans.

I would like to thank Thomas Keffer, the founder of RogueWaveSoftware, for coming up with the idea of writing a book of my own and for supporting and encouraging me ever since. I had been working at his company when he suggested the book project. I was a German alien working at a US corporation when he proposed that I write a book about internationalization in C++. I would like to thank Roland Hartinger, my former supervisor and head of the C++ compiler construction group at Siemens Nixdorf, who threw me into the library project and encouraged me to join the standards committee.

Last, but not least, I thank Klaus Kreft for joining me on this project. Without him this book would have never been finished, and not much is worth doing without him.

--Angelike Langer

First of all, I would like to thank my parents for recognizing and fostering my interest and talent in mathematics and natural sciences. Without their support I would not be who I am. Next I thank two individuals whom I met through my professional work who were true sources of inspiration and insight: Gerhard Draxler, whom I miss tremendously since he retired from his professional life, and Werner Mossner, with whom I had my first contact with IOStreams. Together we implemented a logging facility by derivation from the IOStreams classes.

Finally, I thank Angelika Langer, who is a constant source of ideas and an overwhelmingly persistent workers. Without her effort this book would not have been finished, yet the significance of her contribution is nothing compared to what she means me to me in private life.

--Klaus Kreft



Submit Errata

More Information

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