diff options
author | mmcc <> | 2016-03-12 21:31:22 +0000 |
---|---|---|
committer | mmcc <> | 2016-03-12 21:31:22 +0000 |
commit | d692c27f466b0683d4f7dd5f72058e64e04f0cd4 (patch) | |
tree | 41d48a54c09f49f4e37617cd4f79d217bf4250a8 /src/lib/libcrypto/doc/RSA_set_method.pod | |
parent | b5aa7e790e535fc940826232ac1bf67aeb800cb0 (diff) | |
download | openbsd-d692c27f466b0683d4f7dd5f72058e64e04f0cd4.tar.gz openbsd-d692c27f466b0683d4f7dd5f72058e64e04f0cd4.tar.bz2 openbsd-d692c27f466b0683d4f7dd5f72058e64e04f0cd4.zip |
Remove sentences in RETURN VALUES sections saying that functions with
void return types 'return no value'. This is obvious and therefore
unneccessary to mention.
We spare rewind(3)'s sentence because espie@ pointed out that it's a
warning - the function masks a potential error.
This commit also adds a sentence to X509_free clarifying that it's
NULL-safe. This bit was discussed with doug@.
ok martijn@, sentiment supported by schwarze@
Diffstat (limited to 'src/lib/libcrypto/doc/RSA_set_method.pod')
-rw-r--r-- | src/lib/libcrypto/doc/RSA_set_method.pod | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/lib/libcrypto/doc/RSA_set_method.pod b/src/lib/libcrypto/doc/RSA_set_method.pod index 7f687c8718..3f50a89e5c 100644 --- a/src/lib/libcrypto/doc/RSA_set_method.pod +++ b/src/lib/libcrypto/doc/RSA_set_method.pod | |||
@@ -142,8 +142,6 @@ the default method is used. | |||
142 | RSA_PKCS1_SSLeay(), RSA_PKCS1_null_method(), RSA_get_default_method() | 142 | RSA_PKCS1_SSLeay(), RSA_PKCS1_null_method(), RSA_get_default_method() |
143 | and RSA_get_method() return pointers to the respective RSA_METHODs. | 143 | and RSA_get_method() return pointers to the respective RSA_METHODs. |
144 | 144 | ||
145 | RSA_set_default_method() returns no value. | ||
146 | |||
147 | RSA_set_method() returns a pointer to the old RSA_METHOD implementation | 145 | RSA_set_method() returns a pointer to the old RSA_METHOD implementation |
148 | that was replaced. However, this return value should probably be ignored | 146 | that was replaced. However, this return value should probably be ignored |
149 | because if it was supplied by an ENGINE, the pointer could be invalidated | 147 | because if it was supplied by an ENGINE, the pointer could be invalidated |