I was recently playing with new (3 weeks old) code::blocks release (on 
windows with mingw and msvc) and I must say it is quite solid, although 
there is place for improvement (ie debugger integration could be better, 
tooltips -code completition- sometimes are annoying and  do not want 
want to go away...) But in my oppinion it is much better than devc++ - 
although I have used devc++ about a year ago, this might have changed...

Anyway code::blocks seemd to work fine with gcc (mingw) and msvc, 
although I did not try MS debugger, which probaby does not play so well 
with c::b as gdb (I have trien only gdb). Importing projects from VC 
works very well though...
Main advantage is that c::b is crossplatform (linux (*nix?), mac and 
win), devc++ - to my knowledge - is windows only (written in delphi)

To Pamela:
c::b works fine with fltk.  Just build fltk in the standard way (ie 
using mingw + msys for sh ./configure) and link your project to fltk 
libraries you need. Also install gdb from "technology preview". You can 
also add fluid into the c::b tools to use it with .fl files.
If you want to use gcc-4.2 (which has many additional options if you 
need them - like -mstackrealigh for SSE vars on the stack, ...), install 
gcc-core-4.2.1-sjlj, gcc-g++-4.2.1-sjlj (use sjlj postfix for 
compatibility with gcc-3.5 build libs) and libcc_sjlj_1.dll from 
tarballs and change the compiler to these within Settings->Compiler and 
Debugger->Toolchain executables. If you do not use stl, you might want 
to change g++[-sjlj].exe to gcc[-sjlj].exe for compiling and linking, 
gcc.exe works just fine with c++ files but does not try to link to stl.

Roman


Yuri D'Elia wrote:

> 
> I've never used code:blocks myself extensively, can someone point of the 
> biggest differences between the two in terms of interface advantages?
> 
> Thanks
>