Re: Compiling in mingw-ucrt runtime

[Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>]

> Arthur Miller writes:
>> Just checking if errno was set reduced almost everything; and I found
>> that comment in posix_close aboutt EINTR.
>
> Is this specific to UCRT?  In usual errno usage, errno is not garanteed
> to be 0, because runtime functions do not reset it in case of success.
> If there are no other errors, it often is set to ENOENT, from the time
> when some file was searched along some PATH variable.

On second look, the implementation of close_stream looks fishy to me in
the first place.  Parts of the logic are too convoluted for me to
understand, at least one part does not look right at all.  I do not
think that one should build anything on its setting, not setting or
re-setting errno.