diff options
| author | Werner Koch <[email protected]> | 2016-12-07 22:25:50 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 2016-12-07 22:25:50 +0000 |
| commit | ecb0e3280a7db0e8f6ef395cf64f36a36b15be37 (patch) | |
| tree | 35d686f25ac0e88a43707c77bd938e027e4452ca | |
| parent | Clarify what "checking on bit" means (diff) | |
| download | gpgme-ecb0e3280a7db0e8f6ef395cf64f36a36b15be37.tar.gz gpgme-ecb0e3280a7db0e8f6ef395cf64f36a36b15be37.zip | |
doc: Let's suggest GNU guidelines for bit checking.
--
While educating students we can also get them to use useful habits, in
particular to parenthese bit tests.
Signed-off-by: Werner Koch <[email protected]>
| -rw-r--r-- | doc/gpgme.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/gpgme.texi b/doc/gpgme.texi index ee82b273..511384f9 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -4952,7 +4952,7 @@ signature is valid without any restrictions. This means that you can check for GPGME_SIGSUM_VALID like this: @example -if (sig.summary & GPGME_SIGSUM_VALID) +if ((sig.summary & GPGME_SIGSUM_VALID)) @{ ..do stuff if valid.. @} |