Beginning C++ Through Game Programming, Fourth Edition

<H1>Beginning C++ Through Game Programming, Fourth Edition</H1>
<CENTER>by Michael Dawson, 2015</CENTER>

<OL>
<LI>Chapter 1: Types, Variables, and Standard I/O: Lost Fortune
<LI>This book is for beginners, but that doesn't mean learning C++ will
be easy.
You'll have to read, work, and experiment.
<LI> Although there are literally thousands of computer programming
languages, C++ is the game industry standard.
<LI>In addition to learning about C++ programming, you'll also learn how
to organize your work, break down problems into manageable chunks, and
refine your code.
You'll be challenged at times, but never overwhelmed.
<LI>source code not found at: www.cengageptr.com/downloads 9781305109919
Ask for technical support.
<LI>P.2 Why game programmers choose C++?
    <OL>
    <LI>It's fast.
    <LI>It's flexible.  It supports object-oriented programming, and
    many different styles.
    <LI> It's well-supported.  There's a large pool of available
    graphics APIs and 2D, 3D, physics, and sound engines.
    </OL>
<LI>P.4 Errors
    <OL>
    <LI> Compile errors.  
        <UL>
        <LI>This is also called "syntax errors".  
        <LI>As a
    result, an object file is not produced.  
        <LI>At the beginning you may mostly be stuck by this kind of errors.
        However, you will find that they are the easiest ones to handle,
        because the compiler can detect them for you.
        <LI>Compilers may issue "warnings", too.  Although an object
        file is still generated, you should inspect the reasons which
        trigger the warning, and fix them.
        </UL>
    <LI>Link errors.
        <UL>
        <LI>This indicate that something your program references
        externally cannot be found.
        <LI> These errors are usually solved by adjusting the referenced
        function names or linking the right library.
        </UL>
    <LI> Run-time errors.
        <UL>
        <LI>Even if your program is correct, it can crash at run time if
        divided by zero, or open a non-existing file.
        </UL>
    <LI>Logical errors.
        <UL>
        <LI>These are the most difficult errors to find.
        Your program can run without crashing, but the result is wrong!
        <LI>A good debugging tool may be helpful to identify the
        statements which cause the bug.
        </UL>
    </OL>
<LI>little Endian, IEEE 754
<LI>namespace