GNU bug report logs - #44320
[PATH] [27.1] Make sure send-string-to-terminal send all contents

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: larsi <at> gnus.org, sunlin7 <at> yahoo.com, 44320 <at> debbugs.gnu.org, lin.sun <at> zoom.us
Subject: bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents
Date: Mon, 02 Nov 2020 20:35:57 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: lin.sun <at> zoom.us,  larsi <at> gnus.org,  sunlin7 <at> yahoo.com,
>   44320 <at> debbugs.gnu.org
> Date: Mon, 02 Nov 2020 19:22:21 +0100
> 
> On Nov 02 2020, Eli Zaretskii wrote:
> 
> > But that means 'fwrite' could return zero, if its very first call to
> > 'write' got interrupted, no?
> 
> No.  When an error occurs, it returns EOF.

Is EINTR considered an error for this purpose?  If not, what exactly
is considered an error?  I don't see this clearly documented, so it
could be something we cannot rely on.  In fact, I don't even see in
portable documentation that it will return EOF upon errors, I only see
that the error indication for the stream shall be set and errno shall
be set.

In short, it sounds like calling fwrite in a loop will only work by
sheer luck.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.