cleanup error message handling

The top-level funtion in a thread should print errors using
priv_get_err(), while lower-level functions should set error messages
using priv_set_err() except that error mesesages should be printed
immediately, e.g., under walk_src_path().
This commit is contained in:
Ryo Nakamura
2024-02-07 13:29:45 +09:00
parent 5119d5ae26
commit 96084004b6
6 changed files with 58 additions and 58 deletions

View File

@@ -11,9 +11,12 @@
const char *strerrno(void);
/**
* priv_set_err() sets an error message into a private buffer. This
* error message set by priv_set_err() can be accessed via
* priv_get_err(). priv_*_err functions are not thread safe.
* priv_set_err() sets an error message into a thread-local private
* buffer. This error message can be accessed via priv_get_err().
*
* The top-level function in a thread should print errors using
* priv_get_err(), while lower-level functions should set error
* messages using priv_set_err().
*/
void priv_set_err(const char *fmt, ...);
@@ -26,7 +29,7 @@ void priv_set_err(const char *fmt, ...);
##__VA_ARGS__)
/**
* priv_get_err() gets the error message sotred in a private buffer.
* priv_get_err() gets the error message sotred in the thread-local private buffer.
*/
const char *priv_get_err();