Lines Matching full:functions
57 These functions return a protocol entry. Two types of interfaces are supported:
60 \fBgetprotobynumber()\fR, and \fBgetprotoent()\fR). The reentrant functions can
86 The \fBgetprotobyname_r()\fR and \fBgetprotobynumber_r()\fR functions
93 buffer is used to store returned results. These functions are Unsafe in a
114 \fBgetprotobynumber()\fR functions might leave the enumeration in an
125 efficient, to call more protocol functions after \fBendprotoent()\fR.
142 \fBgetprotobynumber_r()\fR, and \fBgetprotobynumber()\fR functions return a
147 The \fBgetprotoent_r()\fR and \fBgetprotoent()\fR functions return a pointer to
153 \fBgetprotoent_r()\fR functions will fail if:
196 to complete the functionality provided by similar thread-safe functions.
205 \fBgetprotoent_r()\fR functions are reentrant and multithread safe. The
211 functions use static storage, so returned data must be copied if it is to be
213 functions are not safe for multithreaded applications.
216 The \fBsetprotoent()\fR and \fBendprotoent()\fR functions have process-wide