- #1
ineedhelpnow
- 649
- 0
why does cin come AFTER count and not before?
Understanding Cin and Cout Order in C++
- Context: C/C++
- Thread starter ineedhelpnow
- Start date
-
- Tags
- C++
Click For Summary
Discussion Overview
The discussion revolves around the order of the input and output statements in C++, specifically why the cin statement typically follows the cout statement. Participants explore the implications of this order in terms of output visibility and user input.
Discussion Character
- Exploratory
- Technical explanation
- Conceptual clarification
- Debate/contested
Main Points Raised
- Some participants suggest that
coutbuffers output, which may not be displayed until the buffer is flushed, either automatically or by usingendl. - There is a question about the visibility of the
cinstatement, with some participants noting that it does not produce visible output. - Participants inquire about the function of
getline(cin, s), with explanations indicating it reads input until Enter is pressed and stores it in the strings. - Some participants express confusion about the necessity of
cinin certain contexts, questioning if it is needed after acoutstatement. - It is noted that it is common practice to prompt the user with a question using
coutbefore reading input withcin. - One participant concludes that if the goal is only to display the current value of a variable, then reading input afterwards may not be necessary.
Areas of Agreement / Disagreement
Participants generally express confusion and seek clarification on the order of cin and cout, indicating that multiple views exist regarding their usage and necessity in specific contexts. The discussion remains unresolved with varying interpretations of the statements.
Contextual Notes
Some assumptions about the behavior of output buffering and the necessity of input statements may not be fully articulated, leading to differing interpretations among participants.