From 0881633dfd0c530a915cf63be295f00841c94cc4 Mon Sep 17 00:00:00 2001 From: Jonas Nick Date: Wed, 28 Apr 2021 16:57:49 +0000 Subject: [PATCH] secp256k1.h: clarify that by default arguments must be != NULL The same file says that the illegal callback will only triger for violations explicitly mentioned, which is not true without this commit because we often don't mention that an argument is not allowed to be NULL. --- include/secp256k1.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/secp256k1.h b/include/secp256k1.h index d368488..e13f783 100644 --- a/include/secp256k1.h +++ b/include/secp256k1.h @@ -7,7 +7,9 @@ extern "C" { #include -/* These rules specify the order of arguments in API calls: +/* Unless explicitly stated all pointer arguments must not be NULL. + * + * The following rules specify the order of arguments in API calls: * * 1. Context pointers go first, followed by output arguments, combined * output/input arguments, and finally input-only arguments.