Last I used Dev-C++ I believe that it used g++ automatically for C++ projects.
Either way, there is in fact no difference between gcc and g++ other than by default g++, links C++ libraries, whereas with gcc you would have to explicitly link those libraries.
It is not about g++ being more strict that gcc, but rather that the C++ language has stricter rules about what is valid code. Both gcc and g++ can use either C or C++ compilation.
You can force gcc to perform C++ compilation (or even g++ to performs C compilation) regardlless of the file extension with the -x c++
command line option.
Either way, if stricter checking is what you are after, first at least try compiling with -Wall -Werror
, the semantics of C++ code are not identical to C, so if you just want stricter checking, but still want C code, that is possibly the better approach. That said, I would rather recommend embracing C++ fully in any case.
Another issue is that Bloodshed has not maintained Dev-C++ since 2005, you would do well to switch to Orwell Dev-C++
which is the currently maintained fork or Dev-C++. That said, unless they have fixed the abysmal and useless debugger interface, I would suggest Visual C++ Express instead, or Code::Blocks if you want to use GCC/G++ specifically