When comparing Code::Blocks vs Eclipse CDT, the Slant community recommends Eclipse CDT for most people. In the question“What are the best IDEs for C++ on Mac OS X?” Eclipse CDT is ranked 8th while Code::Blocks is ranked 9th. The most important reason people chose Eclipse CDT is:
View values of variables on mouse hover during debugging.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free/Libre/Open Source
Pro Cross platform
Code::Blocks is available for both Windows and Linux, allowing you to use the same IDE across both OSes if you use different machines.
Pro Easy to use
Easy to pick up, for example much easier to include libraries.
Pro Debugger multi-threading support
The debugger supports multi-threaded processes for faster debugging.
Pro Lets you choose the compiler
Code:Blocks lets the developer choose which compiler to use, giving you a higher level of control for on your development workflow.
Pro Nice Mouse Hover assist during debugging
View values of variables on mouse hover during debugging.
Pro Free and open source
Eclipse is an open source project and free to use.
Pro Good font rendering
Because Eclipse is based on SWT, it uses the native font rendering and thus looks better than other IDEs on some Linux systems, where the Java font rendering is not optimal.
Pro Highly customizable
Thanks to the large variety of plugins and various configuration options, Eclipse is very customizable.
Pro Macro definition browser
Cons
Con It's hard to make the code readable
Due to the problems with indention, it's hard to make the code look nice.
Con Poor code completion
The code completion for Code::Blocks is rather poor compared to other IDEs
Con Plugins can be unstable
Though there are plenty of plugins to choose from, they aren't always reliable. Some aren't maintained, bug fixes can be slow, and you may need to download plugins from multiple sources.
Con UI can be confusing
There's an overly abundant presence of menus, this forces you to constantly click around the different menu structures.