frost/secp256k1-zkp
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Clarify that callback can be called more than once

Browse Source
This commit is contained in:
Tim Ruffing
2025-08-20 09:57:10 +02:00
parent d2dcf52091
commit 895f53d1cf
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
include/secp256k1.h
View File

@@ -340,9 +340,9 @@ SECP256K1_API void secp256k1_context_destroy(
* *
* On the other hand, during debug stage, one would want to be informed about * On the other hand, during debug stage, one would want to be informed about
* such mistakes, and the default (crashing) may be inadvisable. * such mistakes, and the default (crashing) may be inadvisable.
* When this callback is triggered, the API function called is guaranteed not * Should this callback return instead of crashing, the return value and output
* to cause a crash, though its return value and output arguments are * arguments of the API function call are undefined. Moreover, the same API
* undefined. * call may trigger the callback again in this case.
* *
* When this function has not been called (or called with fn==NULL), then the * When this function has not been called (or called with fn==NULL), then the
* default handler will be used. The library provides a default handler which * default handler will be used. The library provides a default handler which