![]() |
![]() |
![]() |
|
|
![]() |
HP C
|
Previous | Contents | Index |
declaration: (§3.5)
|
declaration-specifiers: (§3.5)
|
init-declarator-list: (§3.5)
|
init-declarator: (§3.5)
|
storage-class-specifier: (§3.5.1)
|
type-specifier: (§3.5.2)
|
|
struct-or-union-specifier: (§3.5.2.1)
|
struct-or-union: (§3.5.2.1)
|
struct-declaration-list: (§3.5.2.1)
|
struct-declaration: (§3.5.2.1)
|
specifier-qualifier-list: (§3.5.2.1)
|
struct-declarator-list: (§3.5.2.1)
|
struct-declarator: (§3.5.2.1)
|
enum-specifier: (§3.5.2.2)
|
enumerator-list: (§3.5.2.2)
|
enumerator: (§3.5.2.2)
|
type-qualifier: (§3.5.3)
|
declarator: (§3.5.4)
|
direct-declarator: (§3.5.4)
|
pointer: (§3.5.4)
|
type-qualifier-list: (§3.5.4)
|
parameter-type-list: (§3.5.4)
|
parameter-list: (§3.5.4)
|
parameter-declaration: (§3.5.4)
|
identifier-list: (§3.5.4)
|
type-name: (§3.5.5)
|
abstract-declarator: (§3.5.5)
|
direct-abstract-declarator: (§3.5.5)
|
typedef-name: (§3.5.6)
|
initializer: (§3.5.7)
|
initializer-list: (§3.5.7)
|
statement: (§3.6)
|
labeled-statement: (§3.6.1)
|
compound-statement: (§3.6.2)
|
declaration-list: (§3.6.2)
|
statement-list: (§3.6.2)
|
expression-statement: (§3.6.3)
|
selection-statement: (§3.6.4)
|
iteration-statement: (§3.6.5)
|
jump-statement: (§3.6.6)
|
translation-unit: (§3.7)
|
external-declaration: (§3.7)
|
function-definition: (§3.7.1)
|
preprocessing-file: (§3.8)
|
group: (§3.8)
|
group-part: (§3.8)
|
if-section: (§3.8.1)
|
if-group: (§3.8.1)
|
elif-groups: (§3.8.1)
|
elif-group: (§3.8.1)
|
else-group: (§3.8.1)
|
endif-line: (§3.8.1)
|
control-line:
|
lparen: (§3.8.3)
|
replacement-list: (§3.8.3)
|
pp-tokens: (§3.8)
|
new-line: (§3.8)
|
HP C conforms to the ANSI standard for the Programming Language C, as specified by the X3J11 Technical Committee and documented in the American National Standard for Information Systems--Programming Language C (document number: X3.159-1989). HP C has successfully passed the Plum-Hall test suite for ANSI conformance. In strict ANSI C mode, the HP C compiler is a conforming implementation as described by the ANSI C Standard in Section 1.7, Compliance: " A conforming hosted implementation shall accept any strictly conforming program. A conforming implementation can have extensions (including additional library functions), provided they do not alter the behavior of any strictly conforming program. "
The ANSI C Standard defines a strictly conforming program as:
" A strictly conforming program shall use only those features of the language and library specified in this Standard. It shall not produce output dependent on any unspecified, undefined, or implementation-defined behavior, and shall not exceed any minimum implementation limit. "
" An implementation shall be accompanied by a document that defines all implementation-defined characteristics and all extensions. "
As with most language definitions, the ANSI C Standard does not encompass the entire definition of the C language available within an implementation. The C implementations currently supported by HP include a number of features that are not defined in the ANSI C Standard.
The rest of this section describes the compiler's functionality in a format mirroring the outline of the ANSI C Standard. The relevant ANSI C Standard section number is shown in parentheses following each heading. If a heading from the ANSI C Standard is missing from this description, HP C conforms to the Standard exactly, without extension or implementation-defined behavior.
The following sections document only the extensions and implementation-defined portions of the HP C language. Together with the ANSI C Standard, this section completely specifies the HP C implementation of the C language. The ANSI C Standard is referred to as "the Standard" throughout this appendix.
A diagnostic message is produced for the first violation of a syntax rule or constraint specified in the Standard. Subsequent violations are reported if they are not hidden by previous violations.
The semantics of the arguments to main(), including envp, are determined by the programming environment. See your platform-specific HP C documentation for information on arguments to main().
The shift states used for the encoding of multibyte characters are dependent on translation tables available on the local system. A particular character set is supported by the language if the local system's translation tables support it.
Elements within a character constant or string literal of the source character set are mapped directly into the elements of the execution character set. Escape sequences other than those defined by the Standard are diagnosed with a warning and the backslash is ignored, so that the character constant's or string literal's value is the same as if the backslash were not present.
Translation limits vary across platforms because of differences in the underlying machine architecture and operating systems. Otherwise, HP C avoids imposing translation limits.
The following lists show the only limits imposed in HP C. Translation limits listed in the Standard, but not in the following list, are not imposed in HP C:
On Tru64 UNIX systems:
On OpenVMS systems:
HP C's numerical limits are defined in the limits.h and float.h header files. These header files contain the implementation-defined values so that the following descriptions hold:
Any limits not found in the previous list are defined as shown in the Standard.
The __inline, __unaligned, and __restrict keywords are supported on OpenVMS Alpha systems and Tru64 UNIX systems.
All VAX C keywords are supported in VAX C mode. They are:
The following keywords are accepted on Tru64 UNIX systems, but result in a warning:
On Tru64 UNIX systems, globaldef and initialized globalvalue declarations are treated as external definitions. globalref and uninitialized globalvalue declarations are treated as if they were declared extern.
The MAIN_PROGRAM option is also available with the VAX C compatibility option on OpenVMS systems. |
Previous | Next | Contents | Index |
|