Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
Porting UNIX Applications to the OSS Environment
Open System Services Porting Guide—520573-006
7-15
C Compiler Pragmas
Predefined Preprocessor Symbols
The native and TNS C compilers provide three predefined preprocessor symbols:
__TANDEM, __INT32, and __XMEM. (Note that there are two underscores, “__”, at the
beginning of these three preprocessor symbol names.)
You can use __TANDEM to increase the portability of your C programs. (Enclose
system-dependent source text in #ifdef or #ifndef directives to test for the
existence of __TANDEM.)
For the TNS environment, __INT32 (for int defined as 32 bits) is defined by the C
compiler when the WIDE pragma is present; __XMEM (for large memory model) is
defined by the C compiler when the XMEM pragma is present. For the native
environments, these two symbols are always defined.
The TNS/R and TNS/E native C compilers also provide the _TNS_R_TARGET and
_TNS_E_TARGET predefined preprocessor symbols, respectively, which distinguish
them from the TNS C compiler.
C Compiler Pragmas
The #pragma directive is used by C implementations to add preprocessor activities or
provide implementation-defined information to the compiler. The use of pragmas is
completely implementation-dependent. Pragmas are most often used in system header
files. (You will rarely need to add specific pragmas to your program.) Pragmas handle
the interface to the routines maintained in the system-wide library.
_OSS_HOST When defined, the identifiers used by the C
compiler for the OSS environment are identified.
The user does not define or undefine this macro,
it is used only by the compiler.
_OSS_TARGET When defined, the identifiers required for
executing in an OSS environment are identified.
The user does not explicitly define this macro, it
is defined when using the c89
-Wsystype=oss flag.
_IGNORE_LOCALE When defined, macros that support only the
C/POSIX locale are selected, instead of
internationalized functions that support multiple
locales. The macro _IGNORE_LOCALE affects
functions in the ctype.h header file.