diff options
| author | Paul Yang <yang.yang@baishancloud.com> | 2019-02-26 13:11:10 +0800 |
|---|---|---|
| committer | Paul Yang <yang.yang@baishancloud.com> | 2019-02-28 21:38:19 +0800 |
| commit | 4564e77ae9dd1866e8a033f03511b6a1792c024e (patch) | |
| tree | 7cf8a73e48bbc158e8ba7d433f04d3709b4ce562 /doc/man3/BIO_push.pod | |
| parent | 69f6b3ceaba493e70e1296880ea6c93e40714f0f (diff) | |
Place return values after examples in doc
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/8338)
Diffstat (limited to 'doc/man3/BIO_push.pod')
| -rw-r--r-- | doc/man3/BIO_push.pod | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/man3/BIO_push.pod b/doc/man3/BIO_push.pod index 02b6f18182..c5919f3cfd 100644 --- a/doc/man3/BIO_push.pod +++ b/doc/man3/BIO_push.pod @@ -36,6 +36,13 @@ The process of calling BIO_push() and BIO_pop() on a BIO may have additional consequences (a control call is made to the affected BIOs) any effects will be noted in the descriptions of individual BIOs. +=head1 RETURN VALUES + +BIO_push() returns the end of the chain, B<b>. + +BIO_pop() returns the next BIO in the chain, or NULL if there is no next +BIO. + =head1 EXAMPLES For these examples suppose B<md1> and B<md2> are digest BIOs, B<b64> is @@ -62,13 +69,6 @@ by B<md1> and B<md2>. If the call: The call will return B<b64> and the new chain will be B<md1-b64-f> data can be written to B<md1> as before. -=head1 RETURN VALUES - -BIO_push() returns the end of the chain, B<b>. - -BIO_pop() returns the next BIO in the chain, or NULL if there is no next -BIO. - =head1 SEE ALSO L<bio> |