diff options
author | Ulf Möller <ulf@openssl.org> | 2003-11-07 00:07:28 +0000 |
---|---|---|
committer | Ulf Möller <ulf@openssl.org> | 2003-11-07 00:07:28 +0000 |
commit | e6e81c589487cadab8882e4a81609d9c95bba62e (patch) | |
tree | 1cbccbfe5e33ce29e373cfdfd21d721bc3138d02 /doc | |
parent | f75abcefed900d2b729223d87229da09924efd2a (diff) |
oops... the description of ->top was inaccurate (the example is correct though)
Diffstat (limited to 'doc')
-rw-r--r-- | doc/crypto/bn_internal.pod | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/crypto/bn_internal.pod b/doc/crypto/bn_internal.pod index 9805a7c9f2..46abb0547f 100644 --- a/doc/crypto/bn_internal.pod +++ b/doc/crypto/bn_internal.pod @@ -72,7 +72,7 @@ applications. typedef struct bignum_st { - int top; /* index of last used d (most significant word) */ + int top; /* index of last used d (most significant word) + 1 */ BN_ULONG *d; /* pointer to an array of 'BITS2' bit chunks */ int max; /* size of the d array */ int neg; /* sign */ @@ -84,7 +84,7 @@ in size (B<BITS2>), depending on the 'number of bits' specified in C<openssl/bn.h>. B<max> is the size of the B<d> array that has been allocated. B<top> -is the 'last' entry being used, so for a value of 4, bn.d[0]=4 and +is the 'last' entry being used plus one, so for a value of 4, bn.d[0]=4 and bn.top=1. B<neg> is 1 if the number is negative. When a B<BIGNUM> is B<0>, the B<d> field can be B<NULL> and B<top> == B<0>. @@ -202,7 +202,7 @@ call bn_expand2(), which allocates a new B<d> array and copies the data. They return B<NULL> on error, B<b> otherwise. The bn_fix_top() macro reduces B<a-E<gt>top> to point to the most -significant non-zero word when B<a> has shrunk. +significant non-zero word plus one when B<a> has shrunk. =head2 Debugging |