Thread: Newcommer to C++, asking (not) for IDE of choice

Hello everyone.

I'm still learning C++. I do not plan to use this as a career move. Too old to change carreers. Mostly I plan to build on my programming knowledge and use C++ as an hobby to build open source cross-platform apps. My current plan involves a tiered Play by Email Strategy system, others can use to build their worlds, from sci fi to medieval fantasy worlds. Complete with player client app, server,...

Anyways, I'm currently using Dev-C++. I'm planning on using Allegro with AGUP in order to guarantee true cross platform code, others can use to port the system. However, I must say I'm starting to have doubts regarding Dev-C++.

My first problem starts with the debugger interface. It is not very powerful is it? I've downloaded and installed Insight. So I believe I got this problem sorted out. It's a much, much, better interface to gdb... i think... is it?

Next comes the fact Dev-C++ doesn't see an upgrade for well over an year now. Is the development dead? Quite strange giving that the latest version is a beta version.

I've tried also Visual C++ 2005 Express and Visual C++ 6 of which I own a Enterprise Studio license from my VB good ol' days. My fear with these is that they add proprietary libraries to the source code and I can't even seem to be able to install Allegro for VC 6.

What would you choose in case all you wanted was to program for fun and pleasure and wanted to put a real emphasis on open and portable code with the help of libraries the likes of Allegro, wxWidgets and Boost?

Thak you for your time.

I'd use visual C++ 2005. it's by far the best IDE I've encountered.

It is, isn't it? I was fairly impressed with it too. And the debugger is excellent too. I love the ability to change my source code (to an extent) while in debug mode.

Ok, so that is good news. It irked me to no end to see the following as a console source code baseline for a C++ 2005 project:

Code:

#include "stdafx.h"


int _tmain(int argc, _TCHAR* argv[])
{
	return 0;
}

Good to know I can toss all that and program straight code with the standard library, the STL and any other libraries I may choose. No doubt this way, and with both its IDE and debugger features, C++ 2005 becomes a much better solution.

I believe the trick is to separate your code into 3 sections, and compile them separately.

1. Fully-standard portable code (The “meat” of your program).

2. Cross-platform library graphics, etc.

3. System specific libraries, if any.

Thanks Doug!

My perception of a the type of cross-platform code I would like to build is thankfully not very demanding Mostly I want to cover Windows, Linux, FreeBSD and MacOS X. Hence libraries like Allegro and wxWidgets. Let's face it, these days, cross platform development is not rocket science... It's more like lego.

The process by which I will attain portability is similar to what you propose. However, I'm looking more at the functional side of the code. If we look at it, I'm not really doing any cross platform. That has been done for me in those libraries, I'm just making sure I'm not using any system based libraries and that I don't write any machine dependant code. I will though follow a similar strategy to the one you suggest in my code. All bindings between my base code and library specific code will be inside a wrapper, for easier access.

Let's face it, these days, cross platform development is not rocket science... It's more like lego.

The funny thing is... When you go to the computer store, you don't see that many programs available for more than one platform. Or, you find version 6 for Windows and version 5 for Mac. So, I suspect there's a little more to it in the "real world".

No doubt it is. But my little free open source PbeM engine is nothing in comparison to a full blown game from, say Blizzard

As long as I stick to portable libraries to deal with the machine specific parts of a program (graphics and disk access, for instance, to name a couple), I'm sure i'll reduce greatly many of the problems.