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

volume
is the name of the volume to search.
subvolume
is the name of the subvolume to search.
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
Current subvolume and then compiler
subvolume
Current subvolume and then compiler
subvolume
TNS C compiler
N.A.N.A.G-series TNS c89 utility
Current subvolume and then compiler
subvolume
Current subvolume and then compiler
subvolume
TNS/R native C and C++ compilers
N.A.N.A.Native c89 and c99 utilities
Current subvolume and then compiler
subvolume
Current subvolume and then compiler
subvolume
TNS/E native C and C++ compilers
Usage Guidelines
• The SSV pragma can be entered on the compiler RUN command line or in the source text.
• The SSV pragma cannot be used if the compiler is run from the OSS environment. The compiler
issues a warning.
• On the PC platform, you can perform the function of the SSV pragma (specifying the directories
to be searched) on the Project Directories page, available from the Options menu. Enter the
search path in the Include box.
• The enclosing quotation marks are required delimiters around the node, volume, and subvolume
specifications.
• No leading zeros are allowed in the SSV number. Therefore, a specification such as SSV09
is invalid.
• The maximum number of search subvolumes that can be specified in a compilation is 50.
However, the maximum number of characters in the TACL command buffer is 239 characters.
Therefore, it is unlikely that 50 SSVs can be specified on a TACL command line because of
the buffer size limitation.
• SSVs must be specified in ascending sequential order; that is, SSV0, SSV1, SSV2, SSV3,
and so on. If a number is skipped, the TNS C compiler and Cfront ignore the remaining SSVs;
the native compilers, however, process the remaining SSVs.
• Using the native compilers, if you specify SSV pragmas in a source file instead of on the
command line, the numeric order (n) is ignored entirely and the SSV pragmas are processed
in the order encountered.
For example, in a source file you can specify SSVs for the native compilers without regard to
numeric order:
SSV0 "$myvol.subvol0", SSV3 "$myvol.subvol3", SSV4 "$myvol.subvol4"
However, if you enter the preceding SSV pragma list on the command line, only the first SSV
is set; the others are ignored because of the numeric gap.
• The native compilers also support the setting of SSVs using ASSIGN statements. If you use
both ASSIGNs and command-line SSV pragmas, the two sets are unioned together. If the two
sets have any duplicate SSV numbers, the SSV specified in the command line is used.
SSV 245