Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Reference > X

xdr(3N)

HP-UX 11i Version 3: February 2007
» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

xdr — library routines for external data representation

DESCRIPTION

XDR routines allow C programmers to describe arbitrary data structures in a machine-independent fashion. Data for remote procedure calls (RPC) are transmitted using these routines.

Index to Routines

The following table lists XDR routines and the manual reference pages on which they are described:

XDR Routine

Manual Reference Page

xdr_array

xdr_complex(3N)

xdr_bool

xdr_simple(3N)

xdr_bytes

xdr_complex(3N)

xdr_char

xdr_simple(3N)

xdr_control

xdr_admin(3N)

xdr_destroy

xdr_create(3N)

xdr_double

xdr_simple(3N)

xdr_enum

xdr_simple(3N)

xdr_float

xdr_simple(3N)

xdr_free

xdr_simple(3N)

xdr_getpos

xdr_admin(3N)

xdr_hyper

xdr_simple(3N)

xdr_inline

xdr_admin(3N)

xdr_int

xdr_simple(3N)

xdr_long

xdr_simple(3N)

xdr_longlong_t

xdr_simple(3N)

xdr_opaque

xdr_complex(3N)

xdr_pointer

xdr_complex(3N)

xdr_quadruple

xdr_simple(3N)

xdr_reference

xdr_complex(3N)

xdr_setpos

xdr_admin(3N)

xdr_short

xdr_simple(3N)

xdr_sizeof

xdr_admin(3N)

xdr_string

xdr_complex(3N)

xdr_u_char

xdr_simple(3N)

xdr_u_hyper

xdr_simple(3N)

xdr_u_int

xdr_simple(3N)

xdr_u_long

xdr_simple(3N)

xdr_u_longlong_t

xdr_simple(3N)

xdr_u_short

xdr_simple(3N)

xdr_union

xdr_complex(3N)

xdr_vector

xdr_complex(3N)

xdr_void

xdr_simple(3N)

xdr_wrapstring

xdr_complex(3N)

xdrmem_create

xdr_create(3N)

xdrrec_create

xdr_create(3N)

xdrrec_endofrecord

xdr_admin(3N)

xdrrec_eof

xdr_admin(3N)

xdrrec_readbytes

xdr_admin(3N)

xdrrec_skiprecord

xdr_admin(3N)

xdrstdio_create

xdr_create(3N)

MULTITHREAD USAGE

Thread Safe:

Yes

Cancel Safe:

Yes

Fork Safe:

No

Async-cancel Safe:

No

Async-signal Safe:

No

These functions can be called safely in a multithreaded environment. They may be cancellation points in that they call functions that are cancel points.

In a multithreaded environment, these functions are not safe to be called by a child process after fork() and before exec(). These functions should not be called by a multithreaded application that support asynchronous cancellation or asynchronous signals.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2007 Hewlett-Packard Development Company, L.P.