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

SYSTYPE OSS and PCSYSTYPE GUARDIAN
N.A.Not setTNS/R native C and C++ compilers
N.A.N.A.Native c89 and c99 utilities
N.A.Not setTNS/E native C and C++ compilers
Usage Guidelines
• The CPATHEQ pragma can appear only on the compiler RUN command line for the native C
and C++ compilers. For the TNS C compiler and Cfront, the CPATHEQ pragma can appear
either on the compiler RUN command line or in the source file.
• If file-name is omitted, the native compiler searches for a file named CPATHEQ in the same
subvolume as the compiler. Prior to the D45 RVU, the native compilers searched in the default
subvolume of the source file. The TNS compilers also search in the default subvolume.
• For additional guidelines and examples of using a CPATHEQ file with class libraries such as
Tools.h++, see Pragmas for Tools.h++ (page 94).
CPPONLY
The CPPONLY pragma causes only the C macro preprocessor to be run.
CPPONLY [ (option [, option] ) ]
option:
{ [no]comments | [no]lines | file "file-name" }
[no]comments
specifies whether comments are preserved in the preprocessed file.
[no]lines
specifies whether #line directives are generated in the preprocessed file.
file "file-name"
specifies a Guardian type-180 file to receive the preprocessed output. Quotation marks are
required delimiters around the file name.
The default option is comments, lines.
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
N.A.N.A.TNS C compiler
N.A.N.A.G-series TNS c89 utility
Not setNot setTNS/R native C and C++ compilers
N.A.N.A.Native c89 and c99 utilities
Not setNot setTNS/E native C and C++ compilers
Usage Guidelines
• The CPPONLY pragma can appear only on the compiler RUN command line.
• The CPPONLY pragma can be specified only when running the compiler in the Guardian
environment.
• If you do not include the file option, the preprocessed output is written to the OUT file that
was specified in the compiler RUN command. In this case, if the OUT file is an EDIT file,
CPPONLY 181