Lines Matching refs:I
90 =item I<desc>
99 B<SSL_POLL_ITEM> array entry is ignored and I<revents> will be set to 0 on
102 =item I<events>
105 learning about in relation to the resource described by I<desc>. It is a
109 =item I<revents>
112 actually applicable to the resource described by I<desc>. As for I<events>,
115 I<revents> need not be a subset of the events specified in I<events>, as some
122 array need remain allocated only for the duration of the call. I<num_items> must
123 be set to the number of entries in the array, and I<stride> must be set to
128 at this time, where SSL_poll() always returns immediately. As such, I<timeout>
130 In future, other inputs to the I<timeout> argument will result in a blocking
134 The following flags are currently defined for the I<flags> argument:
146 The I<result_count> argument is optional. If it is non-NULL, it is used to
147 output the number of entries in the array which have nonzero I<revents> fields
165 specifying that event type in I<events> is a no-op and will be ignored, and the
166 given event will never be reported in I<revents>.
177 Some event types are non-maskable and may be reported in I<revents> regardless
178 of whether they were requested in I<events>.
192 Where this event is raised on at least one item in I<items>, SSL_poll() will
194 in I<items> with B<SSL_POLL_EVENT_F> set. See L</RETURN VALUES> for more
197 This event type may be raised even if it was not requested in I<events>;
198 specifying this event type in I<events> does nothing.
288 therefore requires the I<timeout> argument be used to specify a zero timeout.
289 Calls to SSL_poll() which specify another value, or which pass I<timeout> as
309 Unless the I<items> pointer itself is invalid, SSL_poll() will always initialise
310 the I<revents> fields of all items in the input array upon returning, even if it
313 If I<result_count> is non-NULL, it is always written with the number of items in
314 the array with nonzero I<revents> fields, even if the SSL_poll() call returns
317 It is possible for I<result_count> to be written as 0 even if the SSL_poll()
321 It is possible for I<result_count> to be written as a nonzero value if the
324 condition while processing a subsequent entry in the I<items> array.
332 "Normal" events representing exceptional I/O conditions which do not
344 If SSL_poll() returns 1 and I<result_count> is zero, the operation timed out
349 If SSL_poll() returns 1 and I<result_count> is nonzero, that many events were
354 If SSL_poll() returns 0 and I<result_count> is zero, the caller has made a basic
359 If SSL_poll() returns 0 and I<result_count> is nonzero, inspect the I<items>
361 raised in I<revents>. The entries added to the ERR stack (of which there is
363 item in I<items> with B<SSL_POLL_EVENT_F> raised. Note that there may be events
364 other than I<SSL_POLL_EVENT_F> output for items which come before the first
367 I<result_count>.
