Elysian Shadows

XianForce wrote:Ok, so let's make this simple and say I have the definition of my cat class in "Cat.h" and then all of its accessor functions/member methods/etc. in "Cat.cpp" then I have my "main.cpp". So with this, where do the includes go, and for what?

#ifndef _cat_h
#define _cat_h

class cat
{
public:
    cat(char* name);
private:
    char* name;
};

#endif

#include "cat.h"
cat::cat(char *name)
{
    this->name = name; //im not sure this will work, you might have to allocate mem for this->name first.
}

#inlcude <stdio.h>
#include <stdlib.h>
#include "cat.h"

int main(void)
{
    cat *meowder = new cat("meowder");
    return 0;
}

XianForce wrote:Yes, thanks that worked, so I have to include the headers in my main.cpp and the .cpp file(s) that are using it?

avansc wrote: ps: ALLWAYS use the #ifndef _filename_h and all that jazz

XianForce wrote:

avansc wrote: ps: ALLWAYS use the #ifndef _filename_h and all that jazz

My IDE automatically does that for me =D. But with your whole thing with the "includes.h" that has all your other header files in it. Wouldn't that take up more memory, and have your program eventually run a lot slower?

Wouldn't that take up more memory, and have your program eventually run a lot slower?

Arce wrote:

Wouldn't that take up more memory, and have your program eventually run a lot slower?

How you structure your program before compiling it won't effect it at all in runtime. In theory, putting your program on a single line, or in 10000 different files should execute the same.

The only difference is compile-time. It will take longer to compile, generate the objects, link, etc.

Arce wrote:Haha. sadly, I just ran into a project setup bitchfest involving misuse of headers and source files...Was killing my linker after switching from BloodShed Dev (at school) to MVC++--one covers multiple declaration checks for ya and the other doesn't.

Luckily, marauder bailed me out...But I gotta tell ya, there's no better way to feel like a shitty programmer than to have a computer scientist critique your code. XDDDD

MauraderIIC wrote: Same thing: more includes per .cpp/.obj = more hard drive use = slower runtime