IPX/SPX Programming Manual

Library Routines
HP NonStop IPX/SPX Programming Manual—528022-001
5-7
Usage/Bind Considerations
°
INT PROC get_errno;
°
INT PROC get_h_errno;
Note that these restrictions imply that the following features are not available in the
C run-time library subset:
•
_MAIN, that is, startup processing, general initialization.
•
Heap management (‘malloc’, ‘calloc’, ‘realloc’, ‘free’) is available only
through the Common Run-Time Environment (CRE) user heap management
routines. Refer to the CRE Programming Manual for details.
If mixed TAL and C code has a TAL MAIN section, the restricted set of functions just
listed applies. If mixed TAL and C code having a C _main is used, full C run-time
library functionality is available.
Usage/Bind Considerations
The following steps summarize TAL usage and bind considerations in a CRE
environment:
1. All addresses must be 32 bits (.EXT).
2. All interactions with socket library (procedures and structures) must use 16-bit
integers (short).
3. Source SOCKPROC to reference socket library procedures.
4. Source SOCKDEFT to reference socket library structures.
5. Specify the CRE compiler directive (ENV COMMON) before compilation.
The following steps summarize pTAL usage and bind considerations in a CRE
environment:
1. All addresses must be 32 bits (.EXT).
2. All interactions with socket library (procedures and structures) must use 32-bit
integers (INT(32)).
3. Source SOCKPROC to reference socket library procedures.
4. Source SOCKDEFT to reference socket library structures.
5. Specify the CRE compiler directive (EXPORT_GLOBALS) before compilation.
TAL to pTAL Conversion Issues
TAL users of the socket library converting to pTAL should use the SRL version of the
socket library, ZINETSRL. For applications unable to run as a CRE compliant
Note. For more information about socket library support for TAL and pTAL applications, see
TALDOCUM in $system.ztcpip.