wireguard-openbsd/lib/libc/stdio/printf.3, branch jd/queueboosts

mop up stdarg rename; ok deraadt

2019-08-30T20:27:25Z

Specify that {v,}asprintf(3) returns precisely -1 on failure,

2019-06-28T14:36:18Z

and that the ret pointer is either unchanged or set to NULL in this case. Since these two functions are not standardized by POSIX, documenting the actual behaviour is the way to go, and the above matches all non-buggy implementations we are aware of. OK millert@ deraadt@

Simplify the description of [v]snprintf(3), move the description

2019-06-27T11:52:59Z

of the return values to RETURN VALUES, deprecate [v]sprintf(3) and fix a punctuation typo. Joint work with and OK millert@.

an -> a;

2019-06-26T22:40:05Z

The POSIX-compatible way of checking for {v,}{f,s,sn,d}printf(3)

2019-06-26T21:13:23Z

failure is with < 0, not the more specific -1 from C discussed at length with millert, nicm, schwarze

For all functions known to be infected by LC_NUMERIC, add short

2019-01-16T12:55:49Z

CAVEATS pointing to the new CAVEATS section in setlocale(3). Make those in wprintf(3) and wscanf(3) more concise since duplicate information is a bad idea. Incompleteness of information originally pointed out by millert@. OK millert@

some grammar fixes; from dholland@netbsd, -r1.68

2018-01-02T08:05:03Z

Consistently .Xr the corresponding wide char functions from char- and

2017-12-01T11:18:40Z

string-handling functions, like we already do it for . Includes a smaller patch from , OK jmc@.

Add dprintf() and vdprintf() RETURN VALUES. OK deraadt@

2017-06-12T18:37:12Z

Add ERRORS section, from FreeBSD. OK tedu@

2016-06-06T17:23:28Z