Dev-C++ bug?

[Null]

I have a strange problem with Dev-C++: i 'can't' compile a project. The problem is, that i can type whole this text into a header file but Dev-C++ will 'compile' happily. To really compile the project and to see errors i have to "Rebuild all" because "Compile and Run" works very 'fine'... But if i make an error in main.cpp and then i press "Compile and Run" then everything is fine - i see an error message.
I don't know what's going on... why dev-c++ can't see errors in header files?

[jsmith]

Is anything including the header file?

[Null]

...!!!##%%*!lol!...
My mistake... I enabled Use fast but imperfect dependency generation
The only reason i've made this is word "fast"...

[mcleano]

Although I do like using Dev-C++ I wish it wasn't discontinued because it does have some annoying bugs. For examlple, int the past I have written a program, comipled it, written another program and when i've gone to compiler it it opens the previous program :S ODD!

And it doesn't do indentations well!

[Null]

I like dev-c++ - it's simple to use and for me that's enough. And, by the way, is gdb debugger so bad as many people say?

[hypercube1]

I never use the debugger, i trace out the whole program in my head. I have a short code

#include <iostream>

using namespace std;

int main(int argc, char *argv[])
{
    bool sdf=true;
    while(sdf)
    {

    }
    return 0;
}

that I plug individual segments of code into to test... like functions I made or classes or whatever. That allows me to break up large codes into small pieces. if the error persists I check how my 'pieces' are interacting. If that fails I come here.
My other issue is that many people give MSVC advice that just doesn't work on dev.

Other than that dev is great, and I like the mingw compiler too

[helios]

I never use the debugger, i trace out the whole program in my head.

You just bumped a month old thread to say something like that?

I have a short code that I plug individual segments of code into to test... like functions I made or classes or whatever. That allows me to break up large codes into small pieces. if the error persists I check how my 'pieces' are interacting.

That's not debugging. That's called "writing software".

If that fails I come here.

That's the real kicker. We're not a debugger. We're here to help when debugging fails.

You're going to have to use the debugger sooner or later, so you might as well start sooner.

My other issue is that many people give MSVC advice that just doesn't work on dev.

Can you give an example? People usually give advice that will work on any platform-compiler-debugger combination unless otherwise required. If such an advice failed it's probably the IDE's fault.