xdr_simple(3N)															    xdr_simple(3N)

NAME

       xdr_simple,  xdr_bool,  xdr_char,  xdr_double,  xdr_enum, xdr_float, xdr_free, xdr_hyper, xdr_int, xdr_long, xdr_longlong_t, xdr_quadruple,
       xdr_short, xdr_u_char, xdr_u_hyper, xdr_u_int, xdr_u_long, xdr_u_longlong_t, xdr_u_short, xdr_void - library  routines  for  external  data
       representation

SYNOPSIS


DESCRIPTION

       XDR  library  routines  allow  C programmers to describe simple data structures in a machine-independent fashion.  Protocols such as remote
       procedure calls (RPC) use these routines to describe the format of the data.

       These routines require the creation of XDR streams (see xdr_create(3N)).

   Routines
       See rpc(3N) for the definition of the data structure.  Note that any buffers passed to the XDR routines must be	properly  aligned.  It	is
       suggested  that	malloc(3C)  be used to allocate these buffers or that the programmer insure that the buffer address is divisible evenly by
       four.

       translates between booleans (C integers)
	      and their external representations.  When encoding data, this filter produces values of either or This routine returns  if  it  suc-
	      ceeds, otherwise.

       translates between C characters
	      and  their  external representations.  This routine returns if it succeeds, otherwise.  Note: encoded characters are not packed, and
	      occupy 4 bytes each.  For arrays of characters, it is worthwhile to consider or (see xdr_complex(3N)).

       translates between C
	      precision numbers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between C
	      (actually integers) and their external representations.  This routine returns if it succeeds, otherwise.

       translates between C
	      and their external representations.  This routine returns if it succeeds, otherwise.

       Generic freeing routine.
	      The first argument is the XDR routine for the object being freed.  The second argument is a pointer to the object itself.  Note: the
	      pointer passed to this routine is not freed, but what it points to is freed (recursively, depending on the XDR routine).

       translates between ANSI C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between C integers
	      and their external representations.  This routine returns if it succeeds, otherwise.

       translates between C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between ANSI C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.  This routine is identical to

       translates between IEEE
	      quadruple precision floating point numbers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between
	      C characters and their external representations.	This routine returns if it succeeds, otherwise.

       translates between unsigned ANSI C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       A filter primitive that translates between a C
	      integer and its external representation.	This routine returns if it succeeds, otherwise.

       translates between C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       translates between unsigned ANSI C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.  This routine is identical to

       translates between C
	      integers and their external representations.  This routine returns if it succeeds, otherwise.

       This routine always returns
	      It may be passed to RPC routines that require a function parameter, where nothing is to be done.

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 and before These functions should not be
       called by a multithreaded application that support asynchronous cancellation or asynchronous signals.

SEE ALSO

       malloc(3C), rpc(3N), xdr_admin(3N), xdr_complex(3N), xdr_create(3N).

																    xdr_simple(3N)