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-16
C Compiler Translation Limits
The following OSS C compiler pragmas are included:
A complete list of all pragmas supported by HP can be found in the C/C++
Programmer’s Guide. The compiler version and SYSTYPE setting determine the
pragma defaults.
C Compiler Translation Limits
A C compiler that conforms to the ISO/ANSI C standard must indicate its translation
limits. The key translation limits and the guaranteed minimums for the native C and
TNS C compilers are contained in the C/C++ Programmer’s Guide.
The native compilers use dynamic data structures, so some program components are
limited by the amount of available memory. If the program you are porting to the OSS
environment doesn’t exceed the guaranteed limits, it should successfully compile with
the native compiler.
C Data Types
The integral data types and the floating point data types supported in the C compilation
environments are specified in limits.h and float.h header files, respectively.
OSS C Run-Time Library
The TNS/R and TNS/E native C run-time libraries used by Open System Services
contains more than 300 predefined macros and functions. The C run-time library
supports both the OSS and Guardian environments. It consists of the complete list of
functions specified by the ISO/ANSI C standard, additional functions specified by the
XPG4 specifications, and functions specific to HP. Many C run-time library functions
are identical, regardless of the environment. However, there are both OSS and
Guardian versions of some functions.
Guardian and OSS API interoperability is provided by making the OSS C and Guardian
C APIs similar to one another. The C run-time library supports two variants of some
functions that support different semantics in the OSS environment from in the Guardian
environment. Environment-specific functions such as fopen() have a variant for each
environment: fopen_oss() and fopen_guardian(). See Environment-Specific
ANSICOMPLY Strict ISO/ANSI C syntax checking (only for G-series TNS C
compiler)
EXTENSIONS HP language extensions are allowed (only for native C compilers)
ANSISTREAMS Odd-unstructured standard I/O files
FUNCTION Attributes of external routines
SYSTYPE Target environment, OSS C compilers default to SYSTYPE OSS
WIDE Data model (default value for SYSTYPE OSS)
NOEXTENSIONS Strict ISO/ANSI C syntax checking (only for native C compilers)