What's the deal with IDE's?
I have used Code::Blocks nightlies as my main IDE since one of its first releases in '05 or '06.
Since I use nightlies and not the stable builds (there are not many of them and they are quickly horribly outdated), there have been issues from time to time with certain builds, such as frequent crashes or features not working properly, but the developers have always responded quickly to any feedback on their forums. If one particular build annoys you, you can always use a former until the issues are fixed (usually does not take more than 1 or 2 newer builds iff you report the issue).
For instance, in the current Windows build (8438), I have issues with CB's "image" freezing as a screen overlay when (sometimes) minimizing, forcing me to restart CB (but everything is saved, so not a big deal), though the Debian build (Jens') is working perfectly.
Like JTippets said, just save often enough, make use of autosave, or do as I and use both (since I will never trust autosaving features ).
Since I use nightlies and not the stable builds (there are not many of them and they are quickly horribly outdated), there have been issues from time to time with certain builds, such as frequent crashes or features not working properly, but the developers have always responded quickly to any feedback on their forums. If one particular build annoys you, you can always use a former until the issues are fixed (usually does not take more than 1 or 2 newer builds iff you report the issue).
For instance, in the current Windows build (8438), I have issues with CB's "image" freezing as a screen overlay when (sometimes) minimizing, forcing me to restart CB (but everything is saved, so not a big deal), though the Debian build (Jens') is working perfectly.
Like JTippets said, just save often enough, make use of autosave, or do as I and use both (since I will never trust autosaving features ).
I use vim, with a few selected plugins.
If you're looking to become a programmer, I would recommend starting with a decent text editor, and then moving to an IDE.
Some will probably disagree with me, but I think you would learn more that way.
If you're looking to become a programmer, I would recommend starting with a decent text editor, and then moving to an IDE.
Some will probably disagree with me, but I think you would learn more that way.
A long time ago I've tried Code::Blocks but couldn't get it to debug. At least not with a gui, maybe some cryptic command line would have helped. But no problems on Eclipse/Qtcreator/VC2010express.
I use Code::Blocks mainly and I've never had it crash once on me. To debug with it, you need to make sure all the debug symbols are enabled and optimizations disabled, and make sure the variable window is actually visible (plus the CPU register window, if you are doing inline assembly) so you can see what's going on. It's not Visual Studio with beautiful mouseover treeview-like displays, but it does work.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement