Re: [Dev-C++] CodeBlocks

[Einar F. <en...@co...>]

G.C.Harmon wrote:

> As much as DevC++ works for me while I attempt to learn C++, is there 
> a good reason not to switch to CodeBlocks if that is where the 
> development is going to be for an IDE? And, by the way, what does a 
> "workspace" do for you?

I havnt found any good reasons not to migrate to Code::Blocks yet, even 
though Code::Blocks havnt reached 1.0 yet (RC2 at the moment). I started 
using it when RC2 arrived and I must say.. it works surprisingly well. 
Both Dev-C++ and Code::Blocks have bugs, but I just found the 
environment in Code::Blocks soo much more confortable!

I guess its more about personal taste. Its easy to adapt to Code::Blocks 
if you are used to Dev-C++. Why not use both? I dont see any problem 
with that. Code::Blocks is basicly Dev-C++2.

A workspace is basicly the idea of having more than one project open at 
the same time so you can swap between them fast. You set the project you 
want to work on as "active". Another advantage with is that you get set 
up multiple build targets with different build rules for each of your 
projects. This is quite practical in many ways. On top of that you can 
build your entire workspace (all open projects) in one operation to any 
or all build targets, and you are ready to play at once. Project files 
are named *.cbp and workspace files are named *.workspace.

Seeing that there probably will be no more maintanace or developement 
for Dev-C++ (sad, but true) I dont see any reason to stay using Dev-C++. 
If you are using Dev-C++ to learn C++ using gcc and installing a few 
devpacks, you can safely migrate to Code::Blocks at once.

Download it an give it a try. It takes minutes or even seconds to get up 
and running with it. Import your Dev.C++ projects and download the 
devpacks you need through the devpack plugin in the plugin menu.

Enjoy :-)

-- 
Einar Forselv