Re: textmode for stdout, what is "correct" now?

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

On Feb 15 19:07, Michael Haubenwallner wrote:
> On 2/15/19 1:48 PM, Corinna Vinschen wrote:
> > On Feb 15 13:03, Michael Haubenwallner wrote:
> >> On 2/15/19 11:22 AM, Corinna Vinschen wrote:
> >>> On Feb 15 08:56, Michael Haubenwallner wrote:
> >>>> On 2/14/19 5:20 PM, Corinna Vinschen wrote:
> >>>>> On Feb 14 16:23, Michael Haubenwallner wrote:
> >>>>>> Hi,
> >>>>>> [SNIP]
> >>>> Down the line in their BIO module they do use setmode(fd, O_TEXT),
> >>>> which is the one that does introduce the \r, as far as I know.
> >>>
> >>> This one is not so nice.  Somebody should tell upstream we only
> >>> want explicit O_BINARY these days, but no explicit O_TEXT.
> 
> To me it sounds strange to use the one but not the other:
> 
> If we don't want O_TEXT at all, isn't O_BINARY obsolete as well,
> so the advise should be to use neither - just like real *nix?

No, on text mode mounts O_BINARY makes sure that the result is
actually a binary file.

> A consequence then might be to deprecate (or even remove) them
> from the public API header files.

As long as we have text mode mounts, no.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]