HP aC++/HP ANSI C Release Notes (B3901-90037; A.06.26; September 2011)

int main() {}
// end of test.c
The following flags are now automatically set with A.05.* and A.06.* compilers:
• -D__HPACC_USING_MULTIPLIES_IN_FUNCTIONAL
• -D__HPACC_THREAD_SAFE_RB_TREE
• -D__HPACC_USING_MULTIPLIES_IN_FUNCTIONAL
• -D__HPACC-FIX_FUNC_ADAPTER_OPERATOR
• -D__HPACC_FULL_ITERATOR_REL_OPS
• -D__HPACC_TEMPLATE_PAIR_CTOR
• -D__HPACC_MEM_FUN_ADAPTOR
Conflict between macros.h and numeric_limits class (min and max)
If your code includes /usr/include/macros.h, note that the min and max macros
defined in macros.h conflict with the min and max functions defined in the
numeric_limits class of the Standard C++ Library. The following code, for example,
would generate a compiler Error 134:
numeric_limits<unsigned int>::max();
If you must use the macros.h header, try undefining the macros that conflict:
...
#include <macros.h>
#undef max
#undef min
...
Known limitations
The following is a list of known limitations for this release. Some of these limitations will
be removed in future releases of HP aC++. Please be aware that some of these limitations
are platform-specific.
• HP aC++ does not support large files (files greater than 2 GB) with <iostream.h>
or <iostream>
• Symbolic debugging information is not always emitted for objects which are not
directly referenced. For instance, if a pointer to an object is used but no fields are
ever referenced, then HP aC++ only emits symbolic debug information for the pointer
type and not for the type of object that the pointer points to. For instance, use of
Widget * only emits debug information for the pointer type Widget * and not
for Widget. If you wish such information, you can create an extra source file which
Conflict between macros.h and numeric_limits class (min and max) 51