C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

• For ISO/ANSI C standard compliance checking, the compiler:
Disables arithmetic overflow traps.◦
◦ Flags HP C language extensions for NonStop systems.
◦ Checks for conformance to the #define preprocessor directive. For a description of the
difference between HP C and the ISO/ANSI C standard, see Chapter 10: Converting
C-Series TNS Programs to Use the Current TNS Compiler.
• The native C and C++ compilers do not support this pragma; use the NOEXTENSIONS pragma
instead.
ANSISTREAMS
The ANSISTREAMS pragma specifies that Guardian files created by the program, including the
standard files (standard input, standard output, and standard error), are odd-unstructured disk files
with a file code of 180. The maximum length of a line for type 180 files is the maximum size of
a file. If this pragma is not asserted, files are EDIT files with a file code of 101.
This pragma enables the compiler to conform to the ISO/ANSI C standard that requires that the
compiler support text files with lines containing at least 254 characters including the terminating
new-line character.
ANSISTREAMS
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
ANSISTREAMSNot setTNS C compiler
ANSISTREAMSANSISTREAMSG-series TNS c89 utility
ANSISTREAMSNot setTNS/R native C and C++ compilers
ANSISTREAMSANSISTREAMSNative c89 and c99 utilities
ANSISTREAMSNot setTNS/E native C and C++ compilers
Usage Guidelines
• ANSISTREAMS is a command-line directive that must be entered on the compiler RUN command
line, not in the source text.
• The ANSISTREAMS directive can also be specified with the -Wallow_cplusplus_comments
flag of the c89 or the c99 utility.
• A text file opened with the ANSISTREAMS pragma in effect cannot be manipulated with the
edfseek(), edftell(), or edlseek() functions.
• Without the ANSISTREAMS pragma, a text line can contain as many as 239 characters.
• The ANSISTREAMS pragma does not affect I/O performed by Guardian procedures.
BASENAME
Information saved in raw data files used for code profiling includes the names of the instrumented
source files used in the creation of those raw data files. By default, these are fully qualified source
file names, following the rules for fully qualified names for the respective host platforms. The
BASENAME option specifies that when the executable object program is run, only the base part
of the source file name will be included in the raw data file. The BASENAME option makes it
possible for source files compiled with the PROFGEN option and the same source files compiled
with the PROFUSE option to be in different locations.
ANSISTREAMS 173