diff options
Diffstat (limited to 'secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3')
| -rw-r--r-- | secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3 | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3 b/secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3 index 32022ed0b083..4b2dfd4531b4 100644 --- a/secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3 +++ b/secure/lib/libcrypto/man/man3/DEFINE_STACK_OF.3 @@ -1,5 +1,5 @@ .\" -*- mode: troff; coding: utf-8 -*- -.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) +.\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45) .\" .\" Standard preamble: .\" ======================================================================== @@ -52,10 +52,13 @@ . \} .\} .rr rF +.\" +.\" Required to disable full justification in groff 1.23.0. +.if n .ds AD l .\" ======================================================================== .\" .IX Title "DEFINE_STACK_OF 3ossl" -.TH DEFINE_STACK_OF 3ossl 2025-09-30 3.5.4 OpenSSL +.TH DEFINE_STACK_OF 3ossl 2026-04-07 3.5.6 OpenSSL .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -136,7 +139,7 @@ This can be used in every header file that references the stack. There are several \fBDEFINE...\fR macros that create static inline functions for all of the functions described on this page. This should normally be used in one source file, and the stack manipulation -is wrapped with application-specific functions. +is wrapped with application\-specific functions. .PP \&\fBDEFINE_STACK_OF()\fR creates set of functions for a stack of \fR\f(BITYPE\fR\fB\fR elements. The type is referenced by @@ -270,7 +273,7 @@ Copying is performed by the supplied \fBcopyfunc()\fR and freeing by \fBfreefunc The function \fBfreefunc()\fR is only called if an error occurs. .SH NOTES .IX Header "NOTES" -Care should be taken when accessing stacks in multi-threaded environments. +Care should be taken when accessing stacks in multi\-threaded environments. Any operation which increases the size of a stack such as \fBsk_\fR\f(BITYPE\fR\fB_insert\fR() or \fBsk_\fR\f(BITYPE\fR\fB_push\fR() can "grow" the size of an internal array and cause race conditions if the same stack is accessed in a different thread. Operations such @@ -353,7 +356,7 @@ and was not a public API. 1.1.1. .PP From OpenSSL 3.2.0, the \fBsk_\fR\f(BITYPE\fR\fB_find\fR(), \fBsk_\fR\f(BITYPE\fR\fB_find_ex\fR() -and \fBsk_\fR\f(BITYPE\fR\fB_find_all\fR() calls are read-only and do not sort the +and \fBsk_\fR\f(BITYPE\fR\fB_find_all\fR() calls are read\-only and do not sort the stack. To avoid any performance implications this change introduces, \&\fBsk_\fR\f(BITYPE\fR\fB_sort\fR() should be called before these find operations. .PP |