generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

GH768: Minor grammar nits in CRYPTO_get_ex_new_index.pod

Browse Source 
Signed-off-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Kurt Roeckx <kurt@openssl.org>
This commit is contained in:
Benjamin Kaduk
2015-12-15 16:23:51 -06:00
committed by Rich Salz
parent d62d17b9c0
commit d3054fb663
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/crypto/CRYPTO_get_ex_new_index.pod
View File

@@ -85,7 +85,7 @@ B<idx> parameter should be an already-created index value.
When setting exdata, the pointer specified with a particular index is saved,
and returned on a subsequent "get" call. If the application is going to
release the data, it must make sure to set a B<NULL> value at the index,
to avoid likely double-free crash.
to avoid likely double-free crashes.
The function B<CRYPTO_free_ex_data> is used to free all exdata attached
to a structure. The appropriate type-specific routine must be used.
@@ -124,9 +124,10 @@ for B<SSL> and B<SSL_SESSION> objects. The B<to> and B<from> parameters
are pointers to the destination and source B<CRYPTO_EX_DATA> structures,
respectively. The B<srcp> parameter is a pointer to the source exdata.
When the dup_func() returns, the value in B<srcp> is copied to the
destination ex_data. If the pointer contained in B<srcp> is not modified,
then both B<to> and B<from> will point to the same data. The B<idx>,
B<argl> and B<argp> parameters are as described for the other two callbacks.
destination ex_data. If the pointer contained in B<srcp> is not modified
by the dup_func(), then both B<to> and B<from> will point to the same data.
The B<idx>, B<argl> and B<argp> parameters are as described for the other
two callbacks.
=head1 RETURN VALUES