summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/buffer/buf_err.c
diff options
context:
space:
mode:
authorschwarze <>2024-12-21 00:27:47 +0000
committerschwarze <>2024-12-21 00:27:47 +0000
commitb3a976914034abf8ea93c958bdb6960d305cabe7 (patch)
tree9aaa25ebd422876764d34de690f555947f2cdf6e /src/lib/libcrypto/buffer/buf_err.c
parentda25826c5f42d94ad45a4d01873ecfffa79a2a8c (diff)
downloadopenbsd-b3a976914034abf8ea93c958bdb6960d305cabe7.tar.gz
openbsd-b3a976914034abf8ea93c958bdb6960d305cabe7.tar.bz2
openbsd-b3a976914034abf8ea93c958bdb6960d305cabe7.zip
Add an EXAMPLES section.
I admit this is unusually long for a manual page. But that's not my fault as a documentation author. An example in a manual page ought to be minimal to show what needs to be demonstrated, and this example is minimal in that sense. Making it shorter without loosing important aspects does not seem possible. When an API is poorly designed, one of the consequences is that that documentation becomes harder to understand and often longer - in this case to the point of becoming outright intimidating. If people dislike that, they should design better APIs in the first place rather than blasting the poor manual page for being too long or too complicated. OK tb@
Diffstat (limited to 'src/lib/libcrypto/buffer/buf_err.c')
0 files changed, 0 insertions, 0 deletions