summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/stack/safestack.h
diff options
context:
space:
mode:
authorschwarze <>2021-12-18 21:11:50 +0000
committerschwarze <>2021-12-18 21:11:50 +0000
commit42346e10e057b7407fa5191c20a0349d35e5b216 (patch)
tree13bdb8949de08d4ec7261c5eabe476012ebdb8d2 /src/lib/libcrypto/stack/safestack.h
parentdf1c42a55e5ce633bf0151349cace8d154ca1af4 (diff)
downloadopenbsd-42346e10e057b7407fa5191c20a0349d35e5b216.tar.gz
openbsd-42346e10e057b7407fa5191c20a0349d35e5b216.tar.bz2
openbsd-42346e10e057b7407fa5191c20a0349d35e5b216.zip
Document BN_abs_is_word(3).
While here, add the missing "const" qualifier to the second parameter of BN_is_word(3) - even though i doubt that marking an integral type parameter as "const" serves any significant purpose... Note that the OpenSSL documentation for this function that Billy Brumley committed on August 4, 2021 is actually wrong. Essentially, it says "BN_abs_is_word() test[s] if a equals ... |w|." Now pray tell me, what exactly is the point of taking the absolute value of an unsigned integer number? To compensate for the obvious absurdity of his patch, Billy made a point of getting *three* OKs from rather notable people: Pauli Dale, Nicola Tuveri, and Dmitry Belyavskiy. I believe this is a striking example of the cavalier attitude some projects put on display when it comes to documentation, and also a striking example of how bad documentation can occasionally be worse than no documentation at all, because the OpenSSL manual page will now thoroughly confuse anyone reading it. SCNR pointing out this (hopefully unintentional) hilarity - or is this an attempt at trolling the readers of their documentation? If it is, they certainly got me.
Diffstat (limited to 'src/lib/libcrypto/stack/safestack.h')
0 files changed, 0 insertions, 0 deletions