Your compiler error is coming from the fact that your signature for the forward declaration of _num_steps does not match the signature of your definition of _num_steps. the type of steps_list does not match Change your prototype line to:
When creating an array like that, its size must be constant. If you want a dynamically sized array, you need to allocate memory for it on the heap and you’ll also need to free it with delete when you’re done: If you want a fixed size, then they must be declared const: Also, doesn’t even provide a … Read more
In the header you have: Which takes 5 arguments, In the source file you have: which takes 6 arguments. It seems like int numCheck does not match the header signature.
You have to use That is because even if it is true that your grid is a pointer, you have allocated in the are pointed by its memory an array of Square object. So when you use the [] operator you are obtaining an object of type Square and not a Square* and for a Square object you hve to use the . operator and … Read more
In C++ == only implemented internally for primitive types and array is not a primitive type, so comparing char[100] and string literal will only compare them as 2 char* or better to say as 2 pointers and since this 2 pointers can’t be equal then items[n] == “ae” can never be true, instead of this you should either use std::string to hold string as: or … Read more
Your first usage of Map is inside a function in the combat class. That happens before Map is defined, hence the error. A forward declaration only says that a particular class will be defined later, so it’s ok to reference it or have pointers to objects, etc. However a forward declaration does not say what members a class has, so as … Read more
Somewhere, somehow, you’re calling the std::string constructor with the const char* value NULL. To avoid the problem. Don’t do that.
For anyone else this might also be because of redefinition of a method or property name. i.e a property and method might have the same name
Your function returns a bool but there’s a potential code path (e.g. z.count is 0) where it may reach the end of the function and return nothing. Hence, the warning issued by the compiler. Add return false; (or return true; but false seems appropriate with your current logic) at the end of your function. As pointed out by others, your else part is also wrong. I’d rewrite it … Read more