wireguard-openbsd/lib/libc/stdio, branch jd/queueboosts

fwide() does not unlock if error was occurred.

2019-12-03T05:03:37Z

ok guenther@ and deraadt

more Version 1 AT&T UNIX history:

2019-09-07T10:28:27Z

a few cases that weren't altogether straightforward; tweak and OK jmc@, OK sobrado@

.Dt same as filename

2019-08-30T23:33:45Z

mop up stdarg rename; ok deraadt

2019-08-30T20:27:25Z

two more syscall == -1 checks

2019-06-29T16:12:21Z

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@

When system calls indicate an error they return -1, not some arbitrary

2019-06-28T13:32:41Z

value < 0. errno is only updated in this case. Change all (most?) callers of syscalls to follow this better, and let's see if this strictness helps us in the future.

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