Class Name "monster" not allowed??

I found this rather weird:

Code:

---

class monster
{
public:
        int hp,maxhp,attack,defense,exp,level;//stats
};
monster monsters;

---

The above code returned these errors:
"E:\Tarasque\Archi\Main.cpp(55) : error C2146: syntax error : missing ';' before identifier 'monsters'
E:\Tarasque\Archi\Main.cpp(55) : error C2501: 'monster' : missing storage-class or type specifiers
E:\Tarasque\Archi\Main.cpp(55) : error C2040: 'monster' : 'int' differs in levels of indirection from 'struct SDL_Surface *'
E:\Tarasque\Archi\Main.cpp(55) : fatal error C1004: unexpected end of file found
Error executing cl.exe.

Archi.exe - 4 error(s), 0 warning(s)"

I found that if you change the class name from "monster" to "montr" or "monster1" (etc etc) it works...just not at "monster"...weird. Any of you have any answers?

//napKIN

I compiled(MSVC) you code without any errors.

Code:

---

#include <iostream>
using namespace std;

class monster
{
public:
        int hp,maxhp,attack,defense,exp,level;//stats
};

int main()
{
        monster monsters;
return 0;
}

---

I was tinkering with it and couldn't get it to work...weird...I just decided to change the name to "npc"

//napKIN

Quote:

---

Originally posted by ripper079
I compiled(MSVC) you code without any errors.

---

Idem Dito, I suggest you make more fail safe, that means
including a constructor, specificly specifying the inheritance.
I know this is all normally not required, but who knows your
compiler might be nuts.

Chances are here just had a surface named monster.

Doh! I forgot my friend was making additions to my code (we are sharing our source on an FTP), and he added an SDL_Surface named...**drum roll**...monster!!! Thanks for all the input guys.

//napKIN

Will this work ?

Code:

---

class monster
{
  public:
    int hp, maxhp, attack, defense, exp, level ; //stats
}
monsters ;

---

Quote:

---

Originally posted by DarkStar
Will this work ?

Code:

---

class monster
{
  public:
    int hp, maxhp, attack, defense, exp, level ; //stats
}
monsters ;

---

---

I'm not sure why you'd want to do this. Every new class you create should go in a header file whereas objects should go in functions or main. In any case, why don't you just try to compile that to find out?

Quote:

---

Originally posted by joshdick
I'm not sure why you'd want to do this. Every new class you create should go in a header file whereas objects should go in functions or main.

---

In napkin111's case, creating a global instance may be the only alternative he has.

In an object orientated language, globals should almost never be used. It ruins the concept of modular programming (in my opinion). I do find myself making static global variabels however, when I need to do something that a file of functions can look at but I don't want the user to know about it. This has it's ups and downs obviously.