Previous | Contents | Index |
specifier-qualifier-list: (§3.5.2.1)
type-specifier specifier-qualifier-listopt |
struct-declarator-list: (§3.5.2.1)
struct-declarator |
struct-declarator: (§3.5.2.1)
declarator |
enum-specifier: (§3.5.2.2)
enum identifieropt {enumerator-list } |
enumerator-list: (§3.5.2.2)
enumerator |
enumerator: (§3.5.2.2)
enumeration-constant |
type-qualifier: (§3.5.3)
const |
declarator: (§3.5.4)
pointeropt direct-declarator |
direct-declarator: (§3.5.4)
identifier |
pointer: (§3.5.4)
* type-qualifier-listopt |
type-qualifier-list: (§3.5.4)
type-qualifier |
parameter-type-list: (§3.5.4)
parameter-list |
parameter-list: (§3.5.4)
parameter-declaration |
parameter-declaration: (§3.5.4)
declaration-specifiers declarator |
identifier-list: (§3.5.4)
identifier |
type-name: (§3.5.5)
specifier-qualifier-list abstract-declaratoropt |
abstract-declarator: (§3.5.5)
pointer |
direct-abstract-declarator: (§3.5.5)
( abstract-declarator ) |
typedef-name: (§3.5.6)
identifier |
initializer: (§3.5.7)
assignment-expression |
initializer-list: (§3.5.7)
initializer |
statement: (§3.6)
labeled-statement |
labeled-statement: (§3.6.1)
identifier : statement |
compound-statement: (§3.6.2)
{ declaration-listopt statement-listopt } |
declaration-list: (§3.6.2)
declaration |
statement-list: (§3.6.2)
statement |
expression-statement: (§3.6.3)
expressionopt ; |
selection-statement: (§3.6.4)
if ( expression ) statement |
iteration-statement: (§3.6.5)
while ( expression ) statement |
jump-statement: (§3.6.6)
goto identifier ; |
translation-unit: (§3.7)
external-declaration |
external-declaration: (§3.7)
function-definition |
function-definition: (§3.7.1)
declaration-specifiersopt declarator declaration-listopt compound-statement |
A.1.3 Preprocessing Directives
preprocessing-file: (§3.8)
groupopt |
group: (§3.8)
group-part |
group-part: (§3.8)
pp-tokensopt new-line |
if-section: (§3.8.1)
if-group elif-groupsopt else-groupopt endif-line |
if-group: (§3.8.1)
#if constant-expression new-line groupopt |
elif-groups: (§3.8.1)
elif-group |
elif-group: (§3.8.1)
#elif constant-expression new-line groupopt |
else-group: (§3.8.1)
#else new-line groupopt |
endif-line: (§3.8.1)
#endif new-line |
control-line:
#include pp-tokens new-line (§3.8.2) |
lparen: (§3.8.3)
the left parenthesis character without preceding white space |
replacement-list: (§3.8.3)
pp-tokensopt |
pp-tokens: (§3.8)
preprocessing-token |
new-line: (§3.8)
the new-line character |
Compaq 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). Compaq C has successfully passed the Plum-Hall test suite for ANSI conformance. In strict ANSI C mode, the Compaq 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, Compaq 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 Compaq C language. Together
with the ANSI C Standard, this section completely specifies the
Compaq 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 Compaq 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,
Compaq C avoids imposing translation limits.
The following lists show the only limits imposed in Compaq C.
Translation limits listed in the Standard, but not in the following
list, are not imposed in Compaq C:
On Tru64 UNIX systems:
On OpenVMS systems:
Compaq 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
.
B.1 Diagnostics (§2.1.1.3)
B.2 Hosted Environment (§2.1.2.2)
B.3 Multibyte Characters (§2.2.1.2)
B.4 Escape Sequences (§2.2.2)
B.5 Translation Limits (§2.2.4.1)
B.6 Numerical Limits (§2.2.4.2)
B.7 Keywords (§3.1.1)
The MAIN_PROGRAM option is also available with the VAX C compatibility option on OpenVMS systems. |
An identifier can include the character dollar sign ($). (A warning is given for this in strict ANSI mode.)
On Tru64 UNIX systems, case distinctions are always significant in an identifier with external linkage.
On OpenVMS systems, all identifier names with external linkage are converted to uppercase by default, but this can be controlled with a command-line option.
Previous | Next | Contents | Index |