Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #163707

Re: ot: on stdin, stdout, stderr and crlf on windows

Show all headers | View raw

Am 05.12.2021 um 00:24 schrieb Meredith Montgomery:
> I know this isn't C.  I'm not aware of any group like
> comp.windows.programmer.  If there is one, I'd appreciate if you set the
> follow-up-to header.  Thank you.
> 
> Windows provides me _setmode(), with which I can put stdout on
> _O_BINARY.  It then stops replacing \n with \r\n.  However, it seems
> that Windows does not do any such replacements on stdin and stderr.  I
> looked for a confirmation of this apparent fact and could not find it.
> 
> Can you advise?  I don't see the replacements taking place; only on
> stdout it seems to happen.
> 
> I'm not sure how to prove that.  Here's my attempt.  This program below
> shows all bytes it reads from stdin.
> 
> C:\tmp>cat show-c.c
> #include <stdio.h>
> 
> int main() {
>    int c;
>    while ( (c = getchar()) != EOF) {
>      printf("%d", c);
>    }
>    printf("\n");
> }
> 
> C:\tmp>show-c.exe < empty.txt
> 10
> 
> So empty.txt must contain at least byte 10.  But if Windows were fixing
> my line-terminations, it should have added a byte 13 (on my back).
> 
> Perhaps I just proved that Windows is not replacing anything on my
> stdin.
> 
> (*) Not sure of the relevance of this
> 
> C:\tmp>file show-c
> show-c: PE32+ executable (console) x86-64, for MS Windows
> 
> Thank you so much.

Check the output of this in your hex-editor:

#include <stdio.h>
#include <fcntl.h>
#include <io.h>
#include <stdlib.h>

int main( int argc, char **argv )
{
	if( argc >= 2 && _setmode( _fileno( stderr ), _O_BINARY ) == -1 )
		return EXIT_FAILURE;
	fprintf( stderr, "it works !\n" );
}

Without a commandline-parameter you've 0x0D, 0x0A
as a line-separator, with you've got only 0x0A.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ot: on stdin, stdout, stderr and crlf on windows Meredith Montgomery <mmontgomery@levado.to> - 2021-12-04 20:24 -0300
  Re: ot: on stdin, stdout, stderr and crlf on windows Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2021-12-05 00:01 +0000
  Re: ot: on stdin, stdout, stderr and crlf on windows Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2021-12-05 00:13 +0000
    Re: ot: on stdin, stdout, stderr and crlf on windows Meredith Montgomery <mmontgomery@levado.to> - 2021-12-04 23:09 -0300
      Re: ot: on stdin, stdout, stderr and crlf on windows Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-12-04 18:27 -0800
      Re: ot: on stdin, stdout, stderr and crlf on windows Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2021-12-05 03:33 +0000
        Re: ot: on stdin, stdout, stderr and crlf on windows Meredith Montgomery <mmontgomery@levado.to> - 2021-12-05 09:17 -0300
  Re: ot: on stdin, stdout, stderr and crlf on windows Bonita Montero <Bonita.Montero@gmail.com> - 2021-12-05 15:04 +0100
  Re: ot: on stdin, stdout, stderr and crlf on windows Bonita Montero <Bonita.Montero@gmail.com> - 2021-12-05 15:13 +0100
    Re: ot: on stdin, stdout, stderr and crlf on windows John Forkosh <forkosh@panix.com> - 2021-12-06 08:20 +0000
      Re: ot: on stdin, stdout, stderr and crlf on windows Bonita Montero <Bonita.Montero@gmail.com> - 2021-12-06 09:45 +0100
      Re: ot: on stdin, stdout, stderr and crlf on windows Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-12-06 10:36 +0000
        Re: ot: on stdin, stdout, stderr and crlf on windows Bonita Montero <Bonita.Montero@gmail.com> - 2021-12-06 13:03 +0100
          Re: ot: on stdin, stdout, stderr and crlf on windows Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-12-06 12:34 +0000
            Re: ot: on stdin, stdout, stderr and crlf on windows Manfred <noname@add.invalid> - 2021-12-06 14:38 +0100
              Re: ot: on stdin, stdout, stderr and crlf on windows Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2021-12-06 06:00 -0800
                Re: ot: on stdin, stdout, stderr and crlf on windows Manfred <noname@add.invalid> - 2021-12-06 18:59 +0100
              Re: ot: on stdin, stdout, stderr and crlf on windows Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-12-06 17:08 +0000
                Re: ot: on stdin, stdout, stderr and crlf on windows scott@slp53.sl.home (Scott Lurndal) - 2021-12-06 17:18 +0000
            Re: ot: on stdin, stdout, stderr and crlf on windows John Forkosh <forkosh@panix.com> - 2021-12-07 01:11 +0000
              Re: ot: on stdin, stdout, stderr and crlf on windows Bart <bc@freeuk.com> - 2021-12-07 09:56 +0000
                Re: ot: on stdin, stdout, stderr and crlf on windows John Forkosh <forkosh@panix.com> - 2021-12-08 08:13 +0000
  Re: ot: on stdin, stdout, stderr and crlf on windows Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-12-10 01:10 -0800
    Re: ot: on stdin, stdout, stderr and crlf on windows gazelle@shell.xmission.com (Kenny McCormack) - 2021-12-10 11:00 +0000

csiph-web