Lines Matching full:these

38   these new APIs to define a fallback code path.
56   The motivation for this is that these functions are intended to support
80     structures (as discussed above) and also intend these functions to be
145   are defined and all of these fields are set to zero on call and on return.
148   which the remote and local addresses are to be filled. If either of these
208     - We would need to include the OS headers which provide these
211     - If we choose to support these functions when OS support is not available
217     - We would need to translate these structures during every call.
221       these allocations probably will need to be on the stack, and therefore
255       Obviously these quantities of iovecs are unrealistically large.
264   - Don't provide these functions and require all users of these functions to
267     - Not providing these functions on OSes that don't support
271       knows when these functions are actually available.)
273   - Provide these functions and emulate the functionality:
278       implementing these would then have to be done by copying buffers around
370 that these are accessing the same data (they are not setters and getters of a
373 to separate these as there is no need for a getter for outgoing packet
374 destination, for example, and by separating these we allow the possibility of
376 we should choose less confusing names for these functions. Maybe
414    (`OPENSSL_malloc`) and flag these datagrams as needing to be freed by OpenSSL,