I think the CDT of eclipse is also a good C/C++ IDE.
http://www.eclipse.org/downloads/index.php
http://www.eclipse.org/cdt/
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/user/faq.html?cvsroot=Tools_Project
http://update.eclipse.org/tools/cdt/releases/new
Can someone compare the advantages and disadvantages of CodeBlocks and "CDT of eclipse"?
IMO (please correct me if i'm missing something)
Debugger:CDT: debugger is very complete and useful
C::B: debugger in this moment is very basic
Project handling:CDT: For simple projects it' ok. For more complex projects, although it's possible to estabilish project dependencies, it does not offer a real multi-target project manager.
C::B: It was a nice surprise for me to find a _real_ multitarget project handling in codeblocks.
Memory OccupationCDT: AAAAARRRGG!!
C::B: Reasonable
Startup TimesCDT: AAAAARRRGG!!
C::B: Very Quick
RefactoryCDT: Present ad seems to works well
C::B: Not present (AFAIK)
Class browsing ecc eccCDT: Very nice and useful _BUT_ i'm really disappointed by C++ indexing times. May be i'm missing something, but trying to handle C::B code with CDT, the first global C++ indexing tooks more than one hour to complete!!
C::B: Present but quite buggy and code completion doesn't handle typedefs and templates.
ExtensibilityCDT: Can be extended with plugins.
C::B: Can be extended with plugins. I quote Yiannis:
Yes, almost everything can be done with plugins. A tutorial on plugins is planned shortly.
FutureCDT: Latest CDT official release is dated Dec 2004. I wasn't able to find any info about CDT delepment process. This open source licensed project is not so "open".
C::B: Yiannis seems to be very active, in development and support. C::B source code hasn't many comments, but it's quite easy to understand. Plugins can extend many aspects of IDE and can be written in C++.
Hope this helps, walter