I think this says as much about djb's abilities as about C's limitations.
out of curiosity, what do you (does he) do if printf fails?
From qmail/qmail-pw2u.c (linked somewhere above):
void die_write()
{
substdio_putsflush(subfderr,"qmail-pw2u: fatal: unable to write output\n");
_exit(111);
}
/* ... */
if (substdio_puts(subfdout,uugh) == -1) die_write();
if (substdio_puts(subfdout,dashcolon) == -1) die_write();
if (substdio_put(subfdout,x,i) == -1) die_write();
/* ... */
Re:Aaron Swartz's Thoughts on djb (2009)
by chris_wot on Saturday March 07, 2015 @07:13AM
(#9161662)
So what does he do when substudio_putsflush has an error?
Well, the process will still exit unconditionally immediately afterwards, attempting to signal an error via its return code. It's hard to do better than that in the context of a real operating system.
Of course, printf() does have a return value ("Upon successful return, these functions return the number of characters printed"), and it can fail... but it takes a considerable consistency of purpose to decide to deal with that possibility explicitly every single time.