HP aC++ is Hewlett-Packard's implementation of the ANSI/ISO C++ International Standard.
The compiler largely
conforms to the standard and is evolving towards full conformance.
Refer to Standardizing Your Code
for listings of standards based features and extensions.
Some of the many supported features are listed here:
New Features in this Release (HP aC++ A.01.l5)
- As you have noticed, this HP aC++ Online Programmer's Guide has been updated from HP CDE
format to HTML format viewable with your HTML browser. Refer to
the +help option.
- The following features as Defined in the ANSI/ISO C++ International Standard:
-
covariant return types
(except for covariant return types with multiply inheriting types)
-
Koenig lookup (You must specify the -Wc,-koenig_lookup,on option.)
- The -I- header file option invokes view-pathing
to override the default -I<directory> option header file search path.
- +m[d] and
+M[d]
options to output the files upon which your source code depends
in a format accepted by the make command.
- +We option allows you to
selectively interpret a warning or future error as an error.
- Additional Options for Verbose Compile and Link Information:
- The __HP_aCC predefined macro identifies the HP aC++ compiler.
- At this release,
+inline_levelnum
option defaults to 1. In the prior versions, A.01.09, A.01.12, A.03.05,
A.03.10, the default was 0, no inlining was done
(the same effect as the +d option).
Release Notes
For the latest information on new features, see the
HP aC++ Release Notes
Migration
If you are migrating code from HP C++ (cfront) to HP aC++,
click here
to find out where to obtain information.
Features Introduced in Prior Releases
The HP aC++ default template instantiation mechanism has changed to
compile-time instantiation (CTTI). For source code containing templates,
the new default may result in faster compile-time processing.
The previous default behavior remains available by specifying the
+inst_auto command-line option when
compiling and linking. If you
provide archive or shared libraries for distribution, you may want
to use +inst_auto to insure consistent behavior between each
distribution of your libraries.
Also, if you provide either archive or shared library products, and your
customers need to use the prior template instantiation default in their
builds, you must build your libraries by using the +inst_auto option.
For More Information
Refer to Using HP aC++ Templates in this
online programmer's guide and to the online
technical document, Using Templates in HP aC++
for details about template instantiation and migration.