Lines Matching refs:I
396 In the description below, B<I<TYPE>> is used
413 B<I<TYPE>_new>() allocates an empty object of the indicated type.
414 The object returned must be released by calling B<I<TYPE>_free>().
416 B<I<TYPE>_new_ex>() is similar to B<I<TYPE>_new>() but also passes the
417 library context I<libctx> and the property query I<propq> to use when retrieving
421 B<I<TYPE>_dup>() copies an existing object, leaving it untouched.
426 To avoid such situations, better use B<I<TYPE>_up_ref>() if available.
428 may be to still call B<I<TYPE>_dup>(), e.g., I<copied_cert = X509_dup(cert)>,
429 followed by I<X509_check_purpose(copied_cert, -1, 0)>,
432 B<I<TYPE>_free>() releases the object and all pointers and sub-objects
435 B<I<TYPE>_print_ctx>() prints the object I<a> on the specified BIO I<out>.
436 Each line will be prefixed with I<indent> spaces.
437 The I<pctx> specifies the printing context and is for internal
439 user-defined, then pass in any I<pctx> down to any nested calls.
443 B<I<TYPE>_new>(), B<I<TYPE>_new_ex>() and B<I<TYPE>_dup>() return a pointer to
446 B<I<TYPE>_print_ctx>() returns 1 on success or zero on failure.