Classes with seperate .h and .cpp file

File: Test.cpp

Code:

---

#include <iostream>
using namespace std;

Test()
{
      name = "Abc";
    cout << name;
}

---

Headerfile:

Code:

---

#ifndef TEST_H
#define TEST_H

class Test                 
{
protected:
    char* name;               

public:
    Test();
};

#include "..\Test.cpp"  //Path is correct

#endif

---

My Main

Code:

---

#include <iostream>
#include "..\HeaderFiles\Test.h" //Path is correct.

int main()
{
cout << "Hello World"; // :D
Test t = new Test();

return 0;
}

---

If I put everything in one file (one header) it works, to then include this into the main.cpp:

Code:

---

#ifndef GREN_H
#define GREN_H

class Test
{
protected:
    char* name;
public:
    Test();
};

Test::Test()
{

}
#endif

---

Edit:
I got this to work! But:
Why can I not do it the way I want to: putting the .cpp file into the header, instead of putting the header into the .cpp file. Am I doing something wrong, or this cannot be done depending on the compiler ("Thats how the compiler is built")?

Writing the top then import the bottom, or writing the bottom to later import the top, should not make a difference? :(

I find this way more logical for me, so really wanna pull this off! :)

The header is a preview of what is defined in the code.

So a .h is a PREVIEW of what is coming - we don't need the code here, bit we know it is defined elsewhere.

The .cpp is the actual working code.

Think of how global functions work you define them at the top of the code then elaborate and write their code at the bottom of the code block. (assuming you are doing them above and below the int main() block).

if you include your cpp file in your .h file you will cause the compiler to compile that code for a second time in it's build process.
As most build process's compile each .cpp file into .obj files.
a .cpp file may not have changed since the last build and is therefore skipped from compilation.
by including your .cpp file into your .h file you cause the compiler to compile all the code even the code in the .obj file is still valid.
To be honest I think you may have problems with builds in larger projects.

Depends how you call the compiler. You do not need to build objects either.

Cprogramming.com FAQ > Multiple source files for one program (C++ example)