getline with cin problem -- multiple returns needed

[Chris]

Running into a problem on Windows. This code

std::string randomStuff;
std::getline(std::cin, randomStuff);

works on unix, but on windows, it requires the user to hit the enter
key *twice* before it continues past the getline. I tried changing the
getline to

std::getline(std::cin, randomStuff, '\n');

but that didn't help. Any ideas?

 

[Marcus Kwok]

Running into a problem on Windows. This code

std::string randomStuff;
std::getline(std::cin, randomStuff);

works on unix, but on windows, it requires the user to hit the enter
key *twice* before it continues past the getline. I tried changing the
getline to

std::getline(std::cin, randomStuff, '\n');

but that didn't help. Any ideas?

Please post a complete and minimal program that demonstrates your
problem. For what it's worth, this program works fine on my system
(Windows XP SP2, compiled with VS .NET 2003 SP1):


#include <iostream>
#include <string>

int main()
{
std::cout << "Enter some text:\n";

std::string randomStuff;
std::getline(std::cin, randomStuff);

std::cout << "\nYou entered:\n\"" << randomStuff << "\"\n";
}

 

[David Harmon]

On 19 Oct 2006 08:09:33 -0700 in comp.lang.c++, "Chris"

Running into a problem on Windows. This code

std::string randomStuff;
std::getline(std::cin, randomStuff);

works on unix, but on windows, it requires the user to hit the enter
key *twice* before it continues past the getline.

I don't believe you. It is something else you haven't shown us that
causes your problem.

This issue is covered in Marshall Cline's C++ FAQ. See the topic
"[5.8] How do I post a question about code that doesn't work
correctly?". It is always good to check the FAQ before posting.
You can get the FAQ at:
http://www.parashift.com/c++-faq-lite/

 

[P.J. Plauger]

On 19 Oct 2006 08:09:33 -0700 in comp.lang.c++, "Chris"


I don't believe you. It is something else you haven't shown us that
causes your problem.

He might be right, if he's using an unpatched V6. See:

http://www.dinkumware.com/vc_fixes.html

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com

 

[Chris]

On 19 Oct 2006 08:09:33 -0700 in comp.lang.c++, "Chris"


I don't believe you. It is something else you haven't shown us that
causes your problem.

I assure you, my pants are not on fire.

 

[Chris]

He might be right, if he's using an unpatched V6. See:

http://www.dinkumware.com/vc_fixes.html

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com

This sounds very likely. We are using VC6. Will investigate further.

 

[Jim Langston]

This sounds very likely. We are using VC6. Will investigate further.

If you are still using VC6 run, don't walk, to the nearest computer store
and pick up a newer compiler (or download a free version).

I used to use VC6 and it just has so many problems because I understand it
preceeded the current standard.

 

[Chris]

If you are still using VC6 run, don't walk, to the nearest computer store
and pick up a newer compiler (or download a free version).

I used to use VC6 and it just has so many problems because I understand it
preceeded the current standard.

Unfortunately, this is the "official compiler" for our product at work.
Companies I work at seem to get frozen on old compilers because they
are scared of upgrading and having to regression test.