First and foremost, allow me to assure you that this post is not meant to discuss the sleep() command, mutexes or semaphores, or using threads. It is meant to address one of the most commonly asked questions by newcomers to C++, especially those who use an IDE for programming.

When my program runs, the execution window closes immediately. What is wrong? How do I hold it open/pause it?

Nothing is wrong - that is exactly what your program has been designed to do - execute, then exit.

When newcomers ask the question above, they are almost always told to use one of the following commands:


Both of the commands above are platform specific solutions, and do not conform to ANSI standards. They use components that are found on certain architectures, but not others. It is preferable to use a solution that does conform to standards, and uses accepted C++ methods.

One such method that is also often recommended is using:

This solution will indeed pause for user input - as long as no characters are currently in the stream. As most applications will have asked for input several times, it is likely that there will be at least one character in the stream (often a newline) that will be captured by the cin.get() method, and the application will continue on past.

There are many ways to do it and remain standards compliant. I will not reinvent the wheel, but will simply post one example already submitted by a member of this site - Xing (hope you don't mind me posting this).

This simple snippet is as follows:

The original submission can be found here:

http://www.dreamincode.net/code/snippet582.htm

This method is standards compliant, and will hold the command window open without invoking any executables that may or may not be present.

Of course, you can always run the program from the command line.

Yeah, if someone refuses to use getc (cin) or sleep, then just run it from the command line... otherwise code a windows interface.

What would be an example of a program that can not use getc (cin) or sleep?

How about if you did something like the following:

may want to include that getch() is part of the #include <conio.h> for c++ otherwise you get a compile error



This post has been edited by Topher84: 19 Jul, 2007 - 07:09 AM

I think my point may have been missed. I advise against the use of getch(). It is a platform dependent function that does not comply to ANSI standards. It is not part of standard C++.

I got your point. There is no conio.h on *nix systems, so the code is not portable.

my bad... i've just always used getch() just because of the easy use and the most we programmed in college were win32 console (as i'd say most people looking for help here are doing also) apps hence no need to include *nix systems. Nice write-up though!

hi..if u use VC++ express edition , simply use Start without DEBUGGING ( Ctrl + F5)..

How would one do so while working in C, not C++?

Snippet shown by me would not work in case of numeric input failures since ignore does not clear the fail state of input stream.. More complete solution could be something like:



This post has been edited by Xing: 6 Aug, 2007 - 10:15 PM

You can wait for user to hit enter using this


This post has been edited by Xing: 6 Aug, 2007 - 10:25 PM

Ahh, thank you thank you! You just helped me out a bunch.

that cleared a lot of my doubts..
good article...

I learned to create a batch file using notepad (when using windows OS)

if the name of my program was "Game_Over" i would type



and i would just execute the batch file. but the only problem is that the name of the exe. file has to be one word.

I tried to bring this point up with someone in my class but not even my teacher understood what I was trying to say.

If you make the program for someone other than yourself, they aren't going to open up your code in an IDE (like Visual XX Express Edition) to run it. They're going to use the little exe file that comes with it like they do for all their other programs. So Ctrl + F5 doesn't work.

...yes but the truth is, as a user, it is really IRRITATING to have to press a key when a program finishes. One of the really nice things about a command line program is they you can put them into a batch file. Then you can use piping to take the output of one program and insert in as the input to another. This becomes problematic if user interaction is needed.

The idea of holding the execution window open is great for assignments, and ok in some programs, but not great for utility programs that a real user may use.

it closes when it goes to the third line
first line hitting return ok
second hitting return it closes

and no2pencil no cin
same as read only?

is there no other way that wont close
even hitting return until you die?

if using c can you just us getchar()?
as long as the buffer is clear anyway?

ok i hope people are still reading this and putting in there input cause i myself am a student and would like new , interesting and just plain standard ways of using C++

http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=01
will be the source of the base of this code...

if you are not using <windows.h> just ignore this post
/* PSUEDO */
add a bool array of 256;
add a MSG;
send to registered WNDPROC
determine wether they key is acceptable or not for exiting or any
other command
and if so exit...

exa:CODE
/* global if you want */
bool keys[256];
/* WINMAIN - just for kicks */
bool exit;
MSG msg; // no further handling needed
/* where you want input without continuing */
while (!exit)
{
if (PeekMessage(&msg,NULL,0,0,PM_REMOVE))
{
// do whatever from send to WNDPROC to asserting the keys here
}
// if you send to WNDPROC(HWND,MSG,HWORD,LWORD) make sure that
// you test when finished ^note there is not bool* so thats why global
// to make sure that exit can be true by
if ( keys[VALUE_FOR_EXIT] ) exit=true;
}

This post has been edited by draike: 2 Feb, 2008 - 11:18 PM

This has definitely helped me out since my school teaches programming concepts in C

I generally (when testing my program) just do


This post has been edited by Sepanto: 22 Mar, 2008 - 03:29 AM