Previous section.
Technical Standard: Networking Services (XNS), Issue 5.2 Draft 2.0
Copyright © 1999 The Open Group
The <xti.h> Header
This chapter describes the effects of including the <xti.h> header file,
which is made available by
each XTI implementation and is included by applications
that use the XTI functions. The data
definitions and macros specified in this chapter need not
be contained in
<xti.h>
itself, but must
be available to the application when
<xti.h>
is included.
There is an example
<xti.h>
header file in
Example XTI Header Files.
- Note:
- Applications written to compilation environments earlier
than those required by this
issue of the specification (see
The Compilation Environment)
and defining _XOPEN_SOURCE
to be less than 500 may have the data structures
and constants of certain protocol
specific headers automatically exposed by the inclusion of
<xti.h>
for compatibility.
The individual protocol-specific appendices document
the providers for which this
may be the case.
Certain symbols or macros may be exposed to applications including
<xti.h>
for compatibility
with applications transitioning from older issues of
this specification where their semantics are
specified. Exposing these symbols or macros is allowed
but not required. Symbols or macros
that may be exposed in this implementation-dependent manner are:
-
-
OPT_NEXTHDR
T_ALIGNhref='#tag_foot_1'>1
All protocol specific symbols exposed through
<xti_osi.h>
as specified in
Use of XTI with ISO Transport Protocols.
All protocol-specific symbols exposed through
<xti_inet.h>
as specified in
Use of XTI with Internet Protocols.
The function definitions in this chapter conform to
the ISO C standard (see referenced documents).
Footnotes
- 1.
- T_ALIGN macro was used only in declaring OPT_NEXTHDR and not
formally specified in XNS4, but XNS4 XTI header test
assertions required it. It is removed as in spirit
it is linked to not requiring OPT_NEXTHDR.