Do people actually still use cin and cout?

Question

This is totally an opinion question. More for chatter. I'm taking some c++ tests and they are littered with cin and cout's.
Do people acutally still use these. I mean I've not seen one in an actual public application ever.

The last question I answered in a test was

int c1;
cout << "Enter numbers: " << flush;
for(int n = 0; cin >> c1; ++n){
   cout << c1 << endl;
}
When does this end..

The correct answer was "when a user hits ctrl+Z". Where in the heck would I press control+Z? I'm assuming in the terminal, I suppose. But honestly. I've not seen the terminal for ages and ages. And I'm sure as heck not going to attempt to program anything for it.

Are questions like this still relevant, in any of our lives?

Answer 1

Yes, you might want to process or transform an input text file. It'll prove handy.

Answer 2

Yes, as long as console applications exist, cout and cin will exist.

Answer 3

Do people acutally still use these. I mean I've not seen one in an actual public application ever.

Define public application. What do you think the command line tools on any *nix use? And yes, we too use them, for our SDKs (at least cout and cerr). cin is often not the best when you have complex enough input -- you are left to write a lexer and a parser of sorts.

Answer 4

It would be more acceptable, from a language standpoint, if the answer to "when will this program end" was "when EOF is received". Just because "Control-Z" is EOF in DOS, does not mean Ctrl-Z is the right answer.

Edit Edited with comment info.

Answer 5

So you want to say that you are a programmer and never used or wrote console application?

Answer 6

Terminals are widely used, and will be used. The reason is that, when used skillfully, they're far more powerful than any GUIs.

Answer 7

No, such questions are not very relevant, but yes, people use std::cin and std::cout all the time. Even the ones who design graphical interfaces may use cout for debugging !

Answer 8

Of course it's relevant.

Many automation and admin scripts on a variety of servers rely on text output/input, for example. This is especially true on *nix systems, not as much on windows now that Powershell has come about with its fancy object support.

Then there are the ones of us (a dying breed, I admit) that pretty much LIVE in the terminal. I use the terminal for about 70-80% of my work. I just find it more natural, faster and more powerful than most related GUI apps.

Answer 9

If you only ever write GUI or Web applications in your career you probably won't have much use for cin and cout. If you ever write anything embedded you'll change your position. You just use a different set of libraries for console apps, text-based apps, GUI apps, and Web apps.

Answer 10

I'd rather use wcin and wcout, at least you get the Unicode stuff.

Answer 11

I've worked on many professional applications and we've not used cin or cout on any of them, even for logging/debugging. Why? Because the stateless *printf methods work perfectly well. One thing I've learned over the years is that stateless trumps statefull for maintainability.