In a header file (generally, a file with an extention of .h or .hpp), the most common approach is to declare classes/functions/etc without providing a definition. Then with a .cpp file of the same name, you provide the definition. eg, You can #include the into your code header the same way as any other library or header file - making sure you provide its path if the header is inside a different directory.

Edit: The above is somewhat incomplete - you should include header guards to stop the file being included twice, ie, The 3 lines highlighted in purple take advantage of the preprocessor, to ensure that everything inbetween the #ifndef and #endif directives can only ever be included once (to include the header file more than once will almost certainly cause a compiler error)

hi, thank you for your answer.
I will try to be more specific, in the book i currently read i see:

file: person.h
why use these directives?what do they mean?

also

file: person.cpp

file: main.cpp
why in main i include only the header file?how does the compiler know where to find find the implementation file....how does it know which implementation file to choose{if i have a lot of files}?
it would seem more logical to include the person.cpp file that has a command to include person.h....

thanks

>>why use these directives?what do they mean?
what directives? on lines 1, 2 and 8? those are called "guard tags" to prevent duplicate declarations if the header file is included more than once. The preprocessor will just ignore the file if it has already been processed. Most of the header files you see nowdays use that technique -- many examples are in the header files installed with your compiler.


>>why in main i include only the header file?how does the compiler know where to find find the implementation file
When you have a project with more than one file you have to tell the compiler's linker what object files have to be included to make the final program. The final executable is made up of either object files (with *.obj files in MS-Windows or *.o in *nix) and the libraries.

If you are using an IDE in MS-Windows environment, such as Dev-C++ or VC++ 2005, then you initially create a project which will contain all the *.cpp and *.h files needed to build the program. And you also have to tell it which libraries to include.

>>it would seem more logical to include the person.cpp file that has a command to include person.h....
that is only for human use, the compiler does not care what *.cpp file(s) you put the implementation code in. And you can have the implementation code in more than one *.cpp file. There is no restriction how you put these together.

main() also needs to include person.h if it wants to instantiate an object of Person class.