Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

building CodeBlocks with M$ VC++ Toolkit 2003

<< < (2/9) > >>

rickg22:
tiwag: I'm the one who put those SANITY_CHECK() macros. They're defined in the sanitycheck.h file. No, I didn't test them with other compilers, so If you could find a way to fix them.... :)

The sanity checks are required to prevent C::B from crashing under certain conditions. (Some events are processed recursively, and this won't be changed unless most ppl vote for it after 1.0-FINAL is released)

CrazyAbbot:
The Sanity Check macro isn't causing the compile to break. however there are many times when you call the macro with no parameters, which causes the compiler to generate a warning.  

It's the managedthread.cpp which causes things to snap.
I havn't had much time to look at it right now because of university etc.  
any clues as to why it's doing that?

rickg22:
Apparently the offending part is:

--- Code: ---
ManagedThread::ManagedThread(bool* abortflag) :
wxThread::wxThread(wxTHREAD_JOINABLE),
m_pAbort(abortflag)

--- End code ---

It's in the constructor part. What I don't get is, how does this thing tell me that the constructor "wxThread::wxThread(wxTHREAD_JOINABLE)" isn't part of wxThread?

Hmmm maybe it's got to do with not having a default constructor. But this is the only way that I could derive from wxThread, since the thread type variable is private  :x

rickg22:
Guys I'm thinking. Maybe we should ask about this particular problem in the wxWidgets forums? Maybe someone could give us a hand.

Urxae:
Hey, I was wondering, why is that second line
--- Code: ---wxThread::wxThread(wxTHREAD_JOINABLE),
--- End code ---
instead of just
--- Code: ---wxThread(wxTHREAD_JOINABLE),
--- End code ---
?

Normally you only need the name of the class in an initializer list, that you're calling the constructor is sort of implied ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page