[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `message' not outputting the newline "atomically"
From: |
Daniele Nicolodi |
Subject: |
Re: `message' not outputting the newline "atomically" |
Date: |
Tue, 2 Jul 2019 09:58:34 +0200 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 |
On 01/07/2019 20:28, Eli Zaretskii wrote:
>> From: Daniele Nicolodi <address@hidden>
>> Date: Mon, 1 Jul 2019 19:01:18 +0200
>>
>> I think you didn't understand my point, and your selective quoting makes
>> me thing you are trying to warp what i wrote in your favor. I was
>> arguing that in the case of a fprintf() with a format string that ends
>> in a new line there is no way to obtain a partial output, with stderr
>> unbuffered or line buffered. On any sane implementation of the c library
>> Either you will get it all or nothing.
>
> And I was saying that this is wrong. With unbuffered stderr, you
> _can_ obtain partial output.
I still disagree. Can you please write a piece of C code that achieves
that, having a fprintf() function call error out, in whichever way you
prefer, such that it's output is partial? I tried to achieve that myself
and I haven't found a way.
Thank you.
Best,
Daniele
Re: `message' not outputting the newline "atomically", Daniele Nicolodi, 2019/07/01