From c840536e1dcec04a71db82d7a5bce64f6a91b495 Mon Sep 17 00:00:00 2001 From: Andrew Kesterson Date: Mon, 12 Jan 2026 09:26:28 -0500 Subject: [PATCH] Fix a couple errors in the README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5bd4649..af3df7e 100644 --- a/README.md +++ b/README.md @@ -64,10 +64,10 @@ The library uses integer values to specify error codes inside of its context. Th You can define additional error types by defining additional `AKERR_xxxxx` values. Error values up to 255 are reserved by the library (`AKERR_xxxxx` begins where `errno` stops), so please begin your error values at 256. When you add additional error codes, you need to define `-DAKERR_MAX_ERR_VALUE=n` to the compiler, where `n` is the maximum error code you have defined. If you define custom error codes, `AKERR_MAX_ERR_VALUE` must be >= 256 or the compiler will throw an error. -Define a human-friendly name for the error with the `error_name_for_status` method somewhere in your code's initialization before the error may be used: +Define a human-friendly name for the error with the `akerr_name_for_status` method somewhere in your code's initialization before the error may be used: ```c -error_name_for_status(129, "Some Error Code Description") +akerr_name_for_status(129, "Some Error Code Description") ``` @@ -150,7 +150,7 @@ void my_logger(const char *fmt, ...) /* set your custom error handler */ -error_log_method = &my_logger; +akerr_log_method = &my_logger; /* proceed to use the library */ ```