Lines Matching +full:non +full:- +full:identical
2 .\" Must use -- eqn -- with this one
23 machinex-independent fashion.
129 program gives identical results on a Sun or a VAX.
157 Identical results can be obtained by executing
168 a need for portable data. Programs can be made data-portable by
183 #include <rpc/rpc.h> /* \fIxdr is a sub-library of rpc\fP */
206 #include <rpc/rpc.h> /* \fIxdr is a sub-library of rpc\fP */
246 Integers are just the tip of the portable-data iceberg. Arbitrary
260 floating-point representation (IEEE), and so on. Any program running on
281 has a disadvantage, but it is unimportant in real-world data transfer
282 applications. Suppose two Little-Endian machines are transferring integers
284 from Little-Endian byte order to XDR (Big-Endian) byte order; the receiving
309 specified, well-documented manner. Thus, it can make sense to use the
313 strings (null-terminated arrays of bytes),
429 if (xdr_long(xdrs, &gp->g_assets) &&
430 xdr_long(xdrs, &gp->g_liabilities))
469 return(xdr_long(xdrs, &gp->g_assets) &&
470 xdr_long(xdrs, &gp->g_liabilities));
574 into a machine-specific representation, or vice-versa.
728 is non-null, then the XDR package assumes
754 Often variable-length arrays of bytes are preferable to strings.
775 are identical to the first, second and third parameters of
793 and the external description of each element is built-in.
797 requires parameters identical to those of
880 return(xdr_string(xdrs, &nup->nu_machinename, NLEN) &&
881 xdr_int(xdrs, &nup->nu_uid) &&
882 xdr_array(xdrs, &nup->nu_gids, &nup->nu_glen,
909 return(xdr_array(xdrs, &pp->p_nusers, &pp->p_len, PLEN,
916 The well-known parameters to
956 return(xdr_array(xdrs, &cp->c_argv, &cp->c_argc, NARGC,
968 return(xdr_array(xdrs, &hp->h_cmds, &hp->h_len, NCMDS,
1018 for fixed-length arrays.
1038 if (!xdr_string(xdrs, &nup->nu_machinename, NLEN))
1040 if (!xdr_int(xdrs, &nup->nu_uid))
1042 if (!xdr_vector(xdrs, nup->nu_gids, NGRPS, sizeof(int),
1098 procedure is called if it is non-null;
1142 return(xdr_union(xdrs, &utp->utype, &utp->uval,
1172 C compilers emit identical discriminant values.
1249 if (xdr_string(xdrs, &pp->name, NLEN) &&
1250 xdr_reference(xdrs, &pp->gnp,
1263 yet some application-specific interpretation applies.
1277 of application-specific pointer interpretation.
1283 meaning to a null-value pointer during serialization.
1319 \&Non-filter Primitives
1320 .IX "XDR" "non-filter primitives"
1344 the routine returns a \-1 in this case
1345 (though \-1 should be a legitimate value).
1357 This routine will also fail if the requested position is out-of-bounds.
1378 .I xdrs->x_op
1384 .I xdrs->x_op
1457 are identical to the corresponding parameters of
1519 (byte count) are identical to the system routines.
1532 * -1 is an error
1663 Use of the resulting buffer is not data-portable.
1676 otherwise. The routines have identical parameters (replace
1700 The higher-level XDR implementation assumes that
1708 otherwise. They have identical parameters:
1756 if (xdr_long(xdrs, &(gp->g_assets)))
1757 return(xdr_long(xdrs, &(gp->g_liabilities)));
1828 return(xdr_gnumbers(xdrs, &gn->gn_numbers) &&
1829 xdr_gnumbers_list(xdrs, &gp->gn_next));
1847 non-recursive one.
1867 if (xdrs->x_op == XDR_FREE) {
1868 nextp = &(*gnp)->gn_next;
1875 gnp = (xdrs->x_op == XDR_FREE) ?
1876 nextp : &(*gnp)->gn_next;
1943 which XDR's all of the non-recursive part. Note that this trick
1947 are identical when passed to
1958 recursive version, this non-recursive routine is far less likely