From: Alejandro Colomar Date: Thu, 19 Mar 2026 00:45:24 +0000 (+0100) Subject: lib/string/README: [v]aprintf(3) are in libc X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=39ccd85823d6dd0873dce6956fad42e1c2cb8023;p=thirdparty%2Fshadow.git lib/string/README: [v]aprintf(3) are in libc [v]aprintf(3) are now part of a libc implementation: gnulib. They are also documented in a manual page. Thus, refer to them as [v]aprintf(3). Signed-off-by: Alejandro Colomar --- diff --git a/lib/string/README b/lib/string/README index 7bd1d3129..b8a231b40 100644 --- a/lib/string/README +++ b/lib/string/README @@ -21,7 +21,7 @@ Don't use some libc functions without Really Good Reasons: asprintf(3) - Use aprintf() instead. + Use aprintf(3) instead. It is difficult to handle errors after asprintf(3). Also, it makes it more difficult for static analyzers to check that memory is later free(3)d appropriately. @@ -209,7 +209,7 @@ strcpy/ - String copying sprintf/ - Formatted string creation - aprintf() + aprintf(3) sprintf(3) variant that allocates. It has better interface than asprintf(3).