[taler-docs] branch master updated: api-common: fix order of fields in GNUNET_CRYPTO_EccSignaturePurpose

[gnunet]

This is an automated email from the git hooks/post-receive script.

mikolai-guetschow pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 0337d0b1 api-common: fix order of fields in 
GNUNET_CRYPTO_EccSignaturePurpose
0337d0b1 is described below

commit 0337d0b116ffe5fba2b4b16b581578d66d03291d
Author: Mikolai Gütschow <mikolai.guetschow@tu-dresden.de>
AuthorDate: Wed Oct 11 16:55:00 2023 +0200

    api-common: fix order of fields in GNUNET_CRYPTO_EccSignaturePurpose
    
    see 
https://docs.gnunet.org/doxygen/d7/d7f/structGNUNET__CRYPTO__EccSignaturePurpose.html
 as reference
---
 core/api-common.rst | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/core/api-common.rst b/core/api-common.rst
index ae4abcc4..6e9db257 100644
--- a/core/api-common.rst
+++ b/core/api-common.rst
@@ -957,9 +957,11 @@ Any piece of signed data, complies to the abstract data 
structure given below.
   /*From gnunet_crypto_lib.h*/
   struct GNUNET_CRYPTO_EccSignaturePurpose {
     /**
-
-    The following constraints apply for a valid amount:
-
+     * This field equals the number of bytes being signed,
+     * namely 'sizeof (struct Data)'.
+     */
+    uint32_t size;
+    /**
      * This field is used to express the context in
      * which the signature is made, ensuring that a
      * signature cannot be lifted from one part of the protocol
@@ -967,11 +969,6 @@ Any piece of signed data, complies to the abstract data 
structure given below.
      * exchange's codebase (git://taler.net/exchange).
      */
     uint32_t purpose;
-    /**
-     * This field equals the number of bytes being signed,
-     * namely 'sizeof (struct Data)'.
-     */
-    uint32_t size;
   };
 
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.