2.9. Primer Summary

What we've covered so far shouldn't be too hard.
If you'd like to experiment, try writing similar programs that
output a few lines. Split your program into a couple of functions and
divide them into two files.

Always enable GCC's warnings when compiling your program.
Warnings mean your code is unclear or incomplete, GCC will guess at
the correct meaning and will usually get it right but you should not
rely on this. Looking at and correcting the warnings will help you
get used to the language. Most warnings are accompanied by the line
number where the problem is. If you can't see anything wrong with
that line check the line above it; if a statement is incomplete GCC
won't notice that it is an error until it encounters the beginning of
the following statement. Don't forget your semi-colons.