Re: toolchain/60432: sh(1) read return code documentation error

The following reply was made to PR toolchain/60432; it has been noted by GNATS.

From: Robert Elz <[email protected]>
To: [email protected]
Cc: 
Subject: Re: toolchain/60432: sh(1) read return code documentation error
Date: Fri, 10 Jul 2026 02:53:00 +0700

     Date:        Thu,  9 Jul 2026 14:40:01 +0000 (UTC)
     From:        "[email protected] via gnats" <[email protected]>
     Message-ID:  <[email protected]>
 
   | 	kre says I/O errors will cause exit status >1.
 
 No, that's not what I said, I said that is what is supposed to
 happen, not what does happen currently.
 
 Currently EOF and read errors are treated identically, as if
 
 	if (read(...) <= 0)
 		return NO_MORE;
 
 I will (sometime not too far away) fix that, both the code, and
 the man page.   These changes will probably not make it into 11.0
 however (unless something delays that more than we'd hope).
 
 That's no huge loss, I've never seen an I/O error from the read
 builtin in any real application.
 
 kre