A part of one of the programs in my assignment requires to declare three arrays of same size which will be used in parallel to store gpa's, registration numbers and names of the students respectively. When I use a single loop to take input in all these three arrays then a strange thing happens. It takes input normally in the gpa and registration number arrays but simply skips the input of the name (a string) and go directly to the next loop. However, if I comment out the other prompts and input lines from this loop and use it to take input solely in the array of names then it works fine.
Please tell me what could be the reason of this problem.
Here is the code that I am using.

#include <iostream>
#include <string>
using namespace std;

int main()
	const int size = 3;
	float Gpa[size];
	unsigned int Reg[size];
	string Name[size];
	for (int i=0; i<size; i++)
		cout << "Enter Registration number of the student no. " << i+1 << ": ";
		cin >> Reg[i];
		cout << "Enter GPA of student no. " << i+1 << ": ";
		cin >> Gpa[i];
		cout << "Enter Name of the sudent no. " << i+1 << ": ";
		getline(cin, Name[i]);

	return 0;

and here is sample run of this program:

Edited by Muhammad Anas: n/a

Attachments strings-array-problem.png 46.74 KB
5 Years
Discussion Span
Last Post by Muhammad Anas

Formatted input (with the >> operator) and unformatted input (getline is an example) don't play well together. It's a subtle combination of features that work together to give you this bug:

  • Requests only block (wait for you to type) if the stream is empty
  • Operator >> first discards leading whitespace
  • Operator >> stops reading when it sees whitespace and doesn't discard it
  • getline() does not discard leading whitespace
  • getline() stops reading when it sees '\n' and does discard it
  • '\n' counts as whitespace, so operator >> stops on it

So what happens is you type the GPA (say 123.45) and hit enter to send input from the command line to cin. cin now contains the string "123.45\n" because the enter key is recognized as the '\n' character.

Operator >> successfully extracts 123.45 and places it in Gpa, but stops when it sees '\n' and leaves that '\n' in the stream for subsequent input requests.

Now getline() is called and sees '\n'. It doesn't block for input because there's already something in the stream, and that something causes getline() to terminate immediately and successfully with an empty string being stored in Name.

That's the "why" of your problem. Now how do you fix it? The best way is not to mix formatted and unformatted input, but if you're new to C++ that might be too much to ask. A simple solution is removing the newline prior to calling getline (an operation we often call flushing the stream):

cin.ignore(1024, '\n');
getline(cin, Name[i]);

The ignore() member function will extract and discard characters up to a count of the first argument or until the second argument is extracted. So this call says to read and throw away up to 1,024 characters or until a '\n' is found. The 1024 part is really little more than a "big enough" value to ensure that everything is cleared out though. A more correct (and also more complex) version is:

// These will be needed along with your other headers
#include <ios> // For streamsize
#include <limits> // For numeric_limits<>

cin.ignore(numeric_limits<streamsize>::max(), '\n');

I mention that only for future reference. A magic number like 1024 will be fine for now.

For a more thorough investigation on flushing the stream, I'll direct you here.

Votes + Comments
this is so great! thanks
thankyou very much for such a detailed and easy to understand explaination of a little bit ricky thing ...

oh ... thankyou very much for such a detailed explaination. It was very easy to understand and worked perfectly.

I tried to read your that sticky article a few minutes ago but I think it is currently a little bit difficult for me to understand.

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.