c++ code organization question

as i come from C# i noticed that we have function's prototypes in c++ in functions, and that in a class i put that and OUTSIDE the class is where i actually put the function's code......but isn't that a bit odd...ugly? how do u guys do? u put each class in a different file so no confusions are made or what? it seems to me a big mess up :o

for example..i see ppl making:

Code:

---

class TESTE {

public:
        int public_int;
        int get_public_int();
        TESTE(int constructor);
};

TESTE::TESTE(int constructor) {
        TESTE::public_int = constructor;
}

int TESTE::get_public_int() {
        return TESTE::public_int;
}

---

although the following way works and for me (coming from C#) seems a lot better because the code gets better organizated

Code:

---

class TESTE {

public:
        int public_int;

        TESTE(int constructor) {
        public_int = constructor;
        }

        int get_public_int() {
                return public_int;
        }
};

---

so..how do u do?

Yes I do it the same way as you do :)
But I can understand why people want to make only a prototype thing, so that someone who didn't write the class can still get a quick overview of what thing the class exposes and uses.

Be aware that when you write the body of a function inside the class declaration it is automatically inlined by the compiler.

Lets say you have classes A and B. B uses A. A's source is some 3000 lines long (little extreme, but it makes the point). B is 30 or 40. A works perfectly, everytime, no bugs, however, B is giving you trouble, so you are debugging it.

Now, if A is written in your style, with the code inside the class declaration itself, the compiler has to compile A's working, 3000 line source file EVERY single time you compile B. This is going to take a LONG time. However, if you simply prototype A in a header file, and put the source in a source file, the source is compiled ONCE, and then linked each time you build your project.

Z.

so i should have 1file only with class prototypes and then each file the classes itselfs?

Quote:

---

Originally posted by Zaei
Lets say you have classes A and B. B uses A. A's source is some 3000 lines long (little extreme, but it makes the point). B is 30 or 40. A works perfectly, everytime, no bugs, however, B is giving you trouble, so you are debugging it.

Now, if A is written in your style, with the code inside the class declaration itself, the compiler has to compile A's working, 3000 line source file EVERY single time you compile B. This is going to take a LONG time. However, if you simply prototype A in a header file, and put the source in a source file, the source is compiled ONCE, and then linked each time you build your project.

Z.

---

Ok didn't know that.. thanks alot, makes things clear :D

I work this way. The class definition I put in a header file (extension .h) ... the definition of my class methods I put in a .cpp file. In this .cpp file you first include the library's you want to use like for example iostream, than you put #include "nameoftheclassdefinition.h" and than you can write the definition of your class methods.

Yet inlining or templating requires you to put function definitions in the header anyway.