| Syntax: | Default: |
| lang(implicitInt[, yes]) lang(implicitInt, no) |
lang(implicitInt[, yes]) |
This option controls whether VisualAge C++ will accept missing or partially specified types as implicitly specifying int. This is no longer accepted in the standard but may exist in legacy code.
With the option set to no, all types must be fully specified.
With the option set to yes, a function declaration at namespace scope or in a member list will implicitly be declared to return int. Also, any declaration specifier sequence that does not completely specify a type will implicitly specify an integer type. Note that the effect is as if the int specifier were present. This means that the specifier const, by itself, would specify a constant integer.
The following specifiers do not completely specify a type.
Note that any situation where a type is specified is affected by this option. This includes, for example, template and parameter types, exception specifications, types in expressions (eg, casts, dynamic_cast, new), and types for conversion functions.
By default, VisualAge C++ sets implicitInt to yes. This is an extension to the C++ standard and gives behavior that is compatible with the C++ compilers provided by earlier versions of VisualAge C++ and predecessor products, and Microsoft Visual C++.
For example, the return type of function MyFunction is int because it was omitted in the following code:
MyFunction()
{
return 0;
}
Set implicitInt to no for compliance with standard C++. For example, the function declaration above must be modified to:
int MyFunction()
{
return 0;
}
![]()
Incremental C++ Build
Configuration Files
![]()
Language Options for C++
Build Options for Compliance With the C++
Standard
Build Options for Compatibility with Old
C++ Compilers
