Sign in to follow this  
Samsonite

DevC++ makes me scream out loud!

Recommended Posts

Samsonite    528
I have never experienced anything like this before. Is it just plain stupidity on my side or a IDE/compilers total inability to allow me to edit a base class after the first compile, i.e removing a destructor? I just removed my destructor from my base object CObject(including it's definition), and I get errors in CBullet.cpp(a derived class) saying "undefined reference" to CObject's destructor, which means it can't find it. Bah. Any ideas as to what might cause this? I'm open for anything.

Share this post


Link to post
Share on other sites
rip-off    10976
Dev-cpp's build system isnt smart enough to force a recompile of dependancies when the file it depends on changes :(. You can go to CBullet.cpp and use "compile current file" and it should work...

Share this post


Link to post
Share on other sites
rip-off    10976
Quote:
Original post by Samsonite
No, that didn't work(but thanks anyway [smile]).

I can make a destructor but keep it empty, is that any good?


Did you do try "Rebuild all"? That could help if the destructor is referenced elsewhere too.

There is no reason why you should be forced into keeping the empty destructor around. The problem is that as far as the compiler is concerned someone is still using the destructor, even though it doesnt exist.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this