Re: `message' not outputting the newline "atomically"

[Eli Zaretskii]

> Cc: address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> Date: Wed, 3 Jul 2019 00:31:18 -0700
> 
> Eli Zaretskii wrote:
> > I'm okay with making 'message' write in one go to stderr, but I don't
> > want to pay the price of having stderr buffered globally.
> 
> I came up with a fix that does all that. Although the fix does not alter the 
> buffering of the stderr stream, it causes 'message' and similar functions to 
> write in one go to avoid interleaving output. It also fixes the problem on 
> AIX 
> and Solaris where a single call to fprintf is implemented by multiple calls 
> to 
> 'write' even if the diagnostic is short, botching interleaving. It also fixes 
> the INT_MAX overflow and memory-allocation issues of the current master's 
> implementation of 'message'.

Whoa!  Is it really worth all that?  Including exposing this to Lisp?

> +#ifndef DOS_NT /* _IOLBF does not work on MS-Windows.  */

This should be WINDOWSNT, as the problem is specific to the
MS-Windows runtime.