You can put class definitions in a .cpp file; but if there are other .cpp files in your project which need that class definition, you will have to #include that first .cpp file.

my_life:          nop          jmp my_life

You can #include anything, the extension is largely irrelevent. Whether it compiles or not is another matter.

#including a cpp file is a generally a bad move and certainly isn't preferred style, because these are understood by the compiler as files that should be compiled and linked. #including these will likely give you a ton of linker errors due to clashing symbols.

In the case of the stl and many of the 'new style' C++ io headers, the files have no extension, so you drop the .h when you #include them.

OK, while the Standard C++ Library headers have no extention, you can use whatever extention you like for your own header files. ".h" or ".hpp" are highly recomended. Some people use ".H" or ".hh" or other crazy things too. No extention for your own headers is generally a bad idea.

When declaring classes, unless it is only going to be used in that one C++ file, it should generally go into a header file. Having a class defined in a C++ file is rare, so you're probably safest putting it into a header.


When you include header files for your project, it generally should look like this:

#include "mything.h"

The < > style brackets are for things in the compiler's include path (rather than relitive to the file the compiler is compiling) - this is basically, all your system and library headers and such.


Also, don't forget include guards on the header. If you don't know what these are, basically put this at the top:

#ifndef MYTHING_H_INCLUDED
#define MYTHING_H_INCLUDED

And this at the bottom:

#endif

Change "MYTHING_H" to whatever the name of your header file is. This prevents the file from being included twice (functionally).