Thread: A few beginner's questions

So you have the declaration right, you just have to not stop. Just as the name itself is a declaration

Code:

int foo(int x); //function declaration

so is the name itself a declaration.

Code:

class Foo; //class declaration

This is also incorrect. The correct syntax to call a static method is:
attack::use

I see and why do I need the ' :: ' operator?
When do I need this and when do I need the ' . ' operator?

But A does not store an object of B, so the definition of B is only needed when defining A::doNothing. C_ntua's point is that that is one example where defining the member function inline will not work, but defining it outside of the class definition will work, assuming that a forward declaration of B is used before defining A. Admittedly, I did not consider this possibility.

I just tested it, it won't work.
If I don't declare class B above class A, I can't have a method in class A that uses class B. Even if I only declare the method in the class and define the body of the method below both classes, I get an error.
This is pretty tricky and will probably cause me headaches in the future.

And when creating a library, I'd just put the definitions of these methods below the class, while still in the same namespace?

As for the methods taking references to an object, I forgot that you can just add * and & to a variable call.
In this case, I'd make a method which takes a memory address of an object and pass that to the method, like this?

Code:

void Test(Object& obj) 
{
     // Do Stuff
}

. . .

Object obj;

Test(&obj);

. . .