questions following upcoming POSIX issue 8 release

[Collin Funk]

Eric Blake <eblake@redhat.com> writes:

> wants to change requirements for isatty() and friends to be required
> to set errno on failure (right now, there is no obvious way to tell,
> using only the standard, if a failure even happened); but the Austin
> Group would like a wider sampling of what existing libc
> implementations do.  If you could run this program on various systems
> and report, that would be helpful:

Running through the different systems on the compile farm:

AIX 7.1.1 (cfarm111):
$ ./a.out 
25 Not a typewriter
25 Not a typewriter
22 Invalid argument

Oracle Solaris 11.3 (cfarm211):
$ ./a.out 
25 Inappropriate ioctl for device
25 Inappropriate ioctl for device
25 Inappropriate ioctl for device

OpenBSD 7.5 (cfarm220):
$ ./a.out                                                              
22 Invalid argument
22 Invalid argument
22 Invalid argument

FreeBSD 14.0 (cfarm240):
$ ./a.out 
22 Invalid argument
22 Invalid argument
22 Invalid argument

Alpine 3.19 w/ Musl (cfarm27):
$ ./a.out 
25 Not a tty
25 Not a tty
0 No error information

MacOS 12.6 (cfarm104):
$ ./a.out 
25 Inappropriate ioctl for device
25 Inappropriate ioctl for device
25 Inappropriate ioctl for device

A NetBSD 10.0 virtual machine:
$ ./a.out 
25 Inappropriate ioctl for device
0 Undefined error: 0
25 Inappropriate ioctl for device

Feel free to send to the POSIX bug tracker. I don't have an account.

Collin