What we didn't do – HP Integrity NonStop J-Series User Manual

Page 18

Advertising
background image

To protect our customers' investment in code written with previous versions of
Tools.h++
.

For example, we have re-engineered the Tools.h++ Version 6.1 collection class templates
to base them on Standard C++ Library containers. In almost all cases, your existing
source code that used classes in the previous version of the library will compile with the
new library without modification.

Design Goal: Smooth Transition

To provide the means for developers to begin moving along the path toward standard
C++ at their own pace and with minimal hassle.

For example, you can use Tools.h++ with or without the Standard C++ Library. If your
development environment supports a version of the Standard C++ Library certified for
use with Tools.h++, we offer 28 new or re-engineered class templates implemented using
the Standard C++ Library container classes. If you don't have the Standard C++ Library,
we offer you a subset interface to many of the same class templates, implemented using
the technology of previous versions of Tools.h++. The appropriate implementation is
selected automatically and transparently at compile time. By coding to the more restricted
interface, you will be able to take full advantage of the Standard C++ Library as soon as
it becomes available to you.

What We Didn't Do

Future versions of Tools.h++ will make full use of the Standard C++ Library and other newly
added features of the C++ language. This version includes several areas where we have elected
to wait before incorporating the latest available technology. In some cases, we're waiting until
the standard library or language feature is more widely available. In other cases, frankly, we're
waiting until we gain more experience with the new features to see how we can best mold them
into a unified and effective whole. We want to be careful not to commit ourselves and our
customers to less than optimal patterns of usage. In the meantime, we'd like to draw your
attention to the following areas:

RWCString

and

RWWString

Tools.h++ continues to use classes

RWCString

and

RWWString

. These classes, along

with their substring classes and collaborating regular expression and tokenizer classes,
have long been considered among the most useful and powerful classes in the library.
This suite of functionality is not offered by the Standard C++ Library. You may use the
C++ standard

string

and

wstring

in your applications, but you may occasionally incur the

overhead of copying if you must convert between Tools.h++ and standard strings.

RWLocale

Tools.h++ continues to use class

RWLocale

. At the time of this release, the C++ standard

locale class specification is still undergoing review by the ANSI/ISO standards

Advertising
This manual is related to the following products: