I guess it was not the perfect place for this kind of stuff, but I am doing OpenGL anyhow, and it`s just for fun Here`s the pic http://www.geocities.com/cippyboy_7/compiler_error.jpg right on the line with the contructor... I thought that MSVC++ 6 would be somehow perfect, I got this kind of message in Dev-C++ 4 also but I did fix it... Now I`m wordless, I`ll try to mess with the names next although I think I must live with out the constructor, if he can`t take it )

That happens whenever your code confuses the compiler beyond its abilities for error-recovery. Just looking at your code, I can see you forgot the parentheses after the constructor name... Whoopsie

A properly-written constructor would be:

GAMESCRIPT::GAMESCRIPT(): nr(0), current_command(0){}

And MSVC6 is far from perfect. I'd even say it is a steaming pile of crap.

---

�Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.� � Brian W. Kernighan

[edited by - Fruny on March 17, 2004 12:18:50 PM]

Thanks a lot
But I still don`t get it... if you don`t put the parantheses... fatal error ?

Edit->I tryed it with some other class... same fatal error at another class it says that something`s wrong

[edited by - cippyboy on March 17, 2004 12:43:57 PM]

I''ve had one of those before. I had to restructure the code a little to get around it. Originally I had:

SendMessage(new Message(WMGIVEFOCUS, "WinMgr", "", 0, new string(MO->GetID()))); 

and I had to change it to:

string Str = MO->GetID();SendMessage(new Message(WMGIVEFOCUS, "WinMgr", "", 0, new string(Str))); 

It''s weird, but just try changing some stuff around a little.

tj963

cippyboy - It just means the your code confused the compiler to the point it cannot continue compiling your program at all. There''s nothing more to it, really.

tj963 - Your code is leaking memory as if there were no tomorrow. If I were you, I''d be ashamed.

---

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” — Brian W. Kernighan

Yeah I''ve had quite a few of those over the years.

Setting a function pointer to the pointer of a static template function within a template class generally does the trick.

| - My project website - | - email me - |

It''s happen to me, and I have VC.NET 2003. I didn''t delcare a destructor for a template class, but I defined it. That killed the compiler.

I think someone should make a "10 easy steps to kill a compiler" article
And it should also include the compilers that can be killed by it, seems like so much fun.
And make tests like->"MSVC++6 was murdered but VC.NET survived"