Understanding Cin and Cout Order in C++

[ineedhelpnow]

why does cin come AFTER count and not before?

 

[I like Serena]

why does cin come AFTER count and not before?

If you print something with count, it is buffered before being shown.
Sometimes you need to flush count's buffer.
Either [m]flush[/m] or [m]endl[/m] will flush count's buffer so you can see it.

 

[ineedhelpnow]

i don't understand. you can't SEE a cin statement though.

also what is a getline statement like getline (cin, s)

 

[I like Serena]

i don't understand. you can't SEE a cin statement though.

Maybe I misunderstood.
What is your question? (Wondering)

also what is a getline statement like getline (cin, s)

It gets input until Enter is pressed.
The result is stored in the string s.

 

[ineedhelpnow]

count << "whatever the heck" << usernum << " is.";
cin >> usernum

why do you do cin after count

cant you just do cin >> s?

 

[I like Serena]

count << "whatever the heck" << usernum << " is.";
cin >> usernum

why do you do cin after count

cant you just do cin >> s?

It's normal to print a question before reading input.
Typically you'd do
[m]count << "Type a usernum: ";
cin >> usernum;[/m]

 

[ineedhelpnow]

oh i see. so for the example i gave cin was not necessary?

 

[I like Serena]

oh i see. so for the example i gave cin was not necessary?

If you only want to print the current value of [m]usernum[/m], there's no point in reading it afterwards.