Learning C through K&R book

I already compiled and ran my first code but there's this thing.
When I run it, cmd flashes and disapears.(I'm using Dev-C++ on windows to make it)
Anyways, I think there was a command or function to make the cmd pause till I press enter or something like that so that I am able to read whatever the output was, the thing is, I cant remember the name of the function or how to write it.
Can one of you tell me which it is, if there is one.
BTW here's my code:


#include <stdio.h>

main ()
{
  printf("Hello World!");
}

>>78
use the EOF. [spoiler]IHBT

>>74
actually EOF is ctrl+Z

>>81
That is system dependent.

>>39
You should always declare the type of your main(). Int is usually enough, as your main() returns the run code (in most cases 0, when program has terminated succesfully). The arguments are for arguments passed from command prompt / terminal - as in, when you execute the program from command prompt like >>40 said, you can add arguments. Example: path\> program.exe arg1 arg2 arg3 etc. Those arguments are then saved in the variable argv[], which is an array of strings (arguments you wrote on the prompt). The first argument (index 0, you'll learn about that when you read about arrays) is always the program's name (program.exe in our case) and the rest are arguments you passed. Argc stands for argcount, aka number of arguments passed to the program. It always equals to at least 1 (remember? The element 0 of array argv is program name), so you can easily check if user specified required amount of options / files.

About return(), you should always add return(0); (or return 0;) to the end of your main. If you use gcc with -Wall flag, you'll get a warning if you don't do this. I recommend setting -Wall and -pedantic flags if you use gcc in your compiler options. (Tools > Compiler Options > tick Add the follwing commands when calling compiler > write -Wall -pedantic > OK in Dev-C++). Though I recommend Code::Blocks if you want to code in C on Windows.

About return(), you should always add return(0); (or return 0;) to the end of your main.

Not always. If the OP does any kind of non-trivial C program in the *nix environment, having the program return(0) may not actually terminate the process. That said, I would just follow what the various C standards say and use

exit(EXIT_SUCCESS);

instead of

return 0;

That way, you could be sure the program would behave as expected across various platforms.