HP aC++ A.03.85 Release Notes

HP aC++ Release Notes
New Features in Version A.03.25
Chapter 1 59
enum x { x1, }; Trailing Comma now Generates Warning 921
Most frequently reported migration issue: enum x { x1, };
The trailing comma is an error, and aC++ now generates Warning 921.
+m[d] and +M[d] Options Have Changed Behavior
Behavior of the +m[d] and +M[d] options has changed. When used with the -E option, only
dependency file information is generated, and there is no preprocessing output.
Behavior when combining the +m[d] or +M[d] option with the -P option is unchanged. Both
dependency information and preprocessing output are generated.
+uc Option for Porting to HP-UX
The +uc option allows you to change the compiler default (signed char) and treat an
unqualified (plain) char data type as unsigned char. This may help in porting code from
other environments to HP-UX.
Predefined String Variable Identifiers for Function Names
As a debugging aid, HP aC++ predefines three string variables for each current function. This
functionality provides compatibility with the C99 standard and with GNU/gcc style coding.
For C99 style coding:
• __func__ indicates the function name as it appears in the source.
For GNU/gcc style coding:
• __FUNCTION__ indicates the function name as it appears in the source.
• __PRETTY_FUNCTION__ indicates the function name, its argument types, and its return
type.
You can use the predefined variables in your code, as in the following examples.
For C99 style coding:
void foo() {
printf(“The function name is %s.\n”, __func__);
}
Output from the example would be:
The function name is foo.