>pressed key and waits for enter to be pressed.Īssuming that's what getchar does. >cin.get() acts the same as getchar() - it echos the Is this that difficult of a concept for you people to grasp? I'm sure it works just fine on your compiler, but because it's non-standard, that means it's not guaranteed to work on my compiler, or someone else's compiler.
>getch() is still available in the conio.h header file (at least in MinGW). You realize the thread is over three years old, yes? That said, any nonstandard function has the implied disclaimer, "use at your own risk"! :p I do try to get them to go the right way first, otherwise it seems to be a much longer journey.
Conio library source code c++ full#
Frankly, if the command shell commands behaved this way, I'd be pretty annoyed: execute two 'dir' commands consecutively, and the second throws away the result of the first - annoying.Īh well, it seems new programmers always must go full circle. Their first goal seems to be clearing the screen. Yet this opinion is revisited thousands of times every year by programmers. It seems a more reasonable approach is to use standard functions that have already taken such issues into account and move forward. The reason it may 'work well' might be because other issues have been overlooked. Then you're back where you started with the standard way. Then you can't have immediate response because you need an "enter" for a 'final' answer. Do you allow the user to make a typing mistake? Then handle the backspace. The problem with unbuffered input is that it becomes the responsibility of the programmer to handle the buffering. I would really love to know if there's any other way to get the functionality of getch()(i.e without using getch()) in the above mentioned cases.
0 kommentar(er)
