Issues with DevC++

Started by
2 comments, last by Rhaythe 16 years, 11 months ago
I have been using DevC++ for a little over a month now and it was working good for class until recently I have run accross some errors that the compier did not catch regarding classes, dynamic arrays and pointers. Is there a way to set warnings for the compier? I had preiously been using Visual Studios 2005 Express Edition and I decided that it was taking too much space on my HD. Any thoughts, suggestions, comments and advise on beter compilers, preferrably small in size is greatly appreciated!!!!
Advertisement
You should still be able to pass -g and -Wall arguments to the linker. That should give you a decent amount of debug material. Be sure "Generate Debug Information" is checked under the linker options, and that should provide those arguments for you (or, just add them yourself to the makefile).

A quick google search churned this up as well:
http://eilat.sci.brooklyn.cuny.edu/cis1_5/HowToDebug.htm
--- ---Current Project: http://source.dev-null-productions.com/tw/"Perhaps the most fundamental problem, however, is that INTJs really want people to make sense."
Quote:
Any thoughts, suggestions, comments and advise on beter compilers, preferrably small in size is greatly appreciated!!!!

Visual Studio is, hands-down, the best IDE available for Windows. Dev-C++ is, hands-down, the worst. Since you don't want to use VS because of its size, I'd suggest checking out Code::Blocks. It's not as good as VS, but its still leaps and bounds better than Dev-C++. Like Dev-C++, Code::Blocks is (I believe) initially set up to use a GCC port for the underlying compiler, but it will likely be a newer version than what ships with Dev-C++, which has been in a state of stagnation for at least a year now.
Quote:Original post by jpetrie
...but it will likely be a newer version than what ships with Dev-C++, which has been in a state of stagnation for at least a year now.

If memory serves, you're correct. It can run on any latest installation of the mingW compiler. Or you can configure it to use the Visual Studio environment. It can operate out of either.

Still, I would prefer Visual Studio Express Edition over both Dev-C++ and Code::Blocks.
--- ---Current Project: http://source.dev-null-productions.com/tw/"Perhaps the most fundamental problem, however, is that INTJs really want people to make sense."

This topic is closed to new replies.

Advertisement