summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/stack
diff options
context:
space:
mode:
authorschwarze <>2024-12-21 00:27:47 +0000
committerschwarze <>2024-12-21 00:27:47 +0000
commit679f7534cf780bb7675823da4bff86ae93d6ea7b (patch)
tree9aaa25ebd422876764d34de690f555947f2cdf6e /src/lib/libcrypto/stack
parent9588bf96d4ac4c99af7b3764a6671ddb6201ca2c (diff)
downloadopenbsd-679f7534cf780bb7675823da4bff86ae93d6ea7b.tar.gz
openbsd-679f7534cf780bb7675823da4bff86ae93d6ea7b.tar.bz2
openbsd-679f7534cf780bb7675823da4bff86ae93d6ea7b.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/stack')
0 files changed, 0 insertions, 0 deletions