On Thu, Dec 21, 2023, at 11:54 PM, Nick Bowler wrote: > On 2023-12-21 19:26, Paul Eggert wrote: >> On 2023-12-21 13:19, Zack Weinberg wrote: >>> Sorry, I'm with GNU here: failure to report errors on writing to >>> stdout is a bug. No excuses will be accepted. >> >> Agreed. printf commands that silently succeed when they can't do the >> requested action are simply broken. > > I tested several modern, current operating systems, including: > OpenBSD 7, NetBSD 9, FreeBSD 13, Alpine Linux 3.15 > I also tested several not-so-modern systems, including: > DJGPP, HP-UX 11, Solaris 8. > > On every single one of these systems, the /usr/bin/printf (or equivalent) > does not generally diagnose errors that occur when writing to standard > output, and an exit status of 0 is returned.
Right, I'm starting a campaign when I get back from vacation in January. (But I'll also see if it's practical to mark this test as an expected failure on systems where the write error isn't detected.) zw
