C Problem, program exits too fast

[silent ben]

/* B Jeater 2005, Program for inputting 2 numbers 
and displaying the result of their multiplication */


#include <stdio.h> /*Standard Library Included*/

int main()

{
	int Interger1;	/*First Number to be Input*/
	int Interger2;	/*Second Number to be Input*/
	int Result;		/*Result of the Multiplication of the Input Numbers*/

	printf ("This Program Will Multiply 2 Numbers Together,\n Please Enter your First Number: ");
	scanf ("%d", &Interger1);	/*Enters First Number*/
	printf ("Please Enter your Second Number: ");
	scanf ("%d", &Interger2);	/*Enters Second Number*/
	
	Result = Interger1 * Interger2;	/*Multiplies the Numbers Together*/

	printf ( "\n\n%d", Interger1);
	printf ( " Multiplied by ");
	printf ( "%d", Interger2);
	printf ( " Equals ");
	printf ( "%d", Result);
	printf ( "\n");

	cin.get();

	return 0;

}

When i run that piece of code, it waits for the 2 inputs, then it works out the correct number, but doesn't give me time to see the answer before closing the command prompt . I thought that the cin.get would stop the program until I hit another key, but it didn't

Can someone help me out?

[herulach]

easiest solution is to just run the program from a caommand prompt.

[Paul Adams]

For temporary debugging "wait for keypress" code I think I used to use:

#include <conio.h>
...
while (!kbhit());

Although kbhit() might be one of those Borland & Microsoft specific functions (not ANSI C).

I think it's some issue with the keyboard buffer not being empty, so get() functions return a result immediately - I think there's a function for clearing the buffer manually to avoid this problem.

[Norky]

Try adding a do loop around the whole thing for a "Try again? y/n" sort of affair

[TheAnimus]

This is actually upto the shell as to what to do, some guy claimed i failed my BIO first round exams because i didn't put some yes/no wait on loop at the end.

If you run it via CMD, then command will retain the output for you.

Its not considered the "done thing" to wait for the output in code, all standard utils dont (eg ipconfig)

If your doing some marking of code with lotsa exe's, it would possible to tell windows to asociate .exe with a program of your making, which quickly looks at the code to see if its a console program, and if so run's it via cmd, if not runs it normally. Might be a handy tool to make some time (add's to list).

[yamangman]

Whack a getch(); in there?

[5lab]

just run it from a command prompt.. winkey-r...cmd

[Spud1]

or....

assuming your using Visual Studio to do this, just run it by pressing F5, should wait before closing

ie run it in debug mode ;p works great


Temp work around is to add in a scanf or something but its a dirty way try running in debug mode first, only real diff between compiling/running that way to a release on is that VS generates a tonne of cr@p to go with it, but unless you have a 2meg hard disk its not an issue