9

Well, the subject says it all, basically.

I have a command-line utility that may be used interactively or in scripts, using pipes or i/o redirection. I am using cin and cout for i/o, and I want to write an extra EOL at the end if the output is console, so that user prompt will start from the next line. Within scripts this would be harmful.

Can I assume cin == 0, cout == 1? I understand that there is no clean way to get the file descriptor of a stream. Or is it?

davka
  • 13,974
  • 11
  • 61
  • 86

2 Answers2

19

If using Linux (and probably other unixes, but definitely not Windows) you could try isatty.

There's no direct way of extracting the file descriptor from the C++ stream. However, since in a C++ program both cout as well as stdout exist and work at the same time (C++ by default provides synchronisation between stdio and iostream methods), your best bet in my opinion is to do a isatty(fileno(stdout)).

Make sure you #include <unistd.h>.

Dan
  • 3,490
  • 2
  • 22
  • 27
  • 2
    You can use [`_isatty`](http://msdn.microsoft.com/en-gb/library/f4s0ddew) on Windows – Matt Clarkson Mar 12 '13 at 09:51
  • On Windows, you'd use [`GetFileType`](http://msdn.microsoft.com/en-us/library/windows/desktop/aa364960%28v=vs.85%29.aspx) Console, file, and disk can all be differentiated. – Ben Voigt Mar 16 '14 at 21:02
6

It is possible to use rdbuf() to change the destination of std::cin and std::cout inside your program. If you don't do that, it is probably quite safe to assume that cin = 0, cout=1 and clog and cerr both = 2 as the C++ standard states that they are synchronized with C stdin, stdout and stderr and those have per POSIX those file descriptors at startup.

AProgrammer
  • 51,233
  • 8
  • 91
  • 143