> .NET
> Cons: may not be available on your target platform
I've been looking at Mono, which is a C# compiler and
a portable JIT CLR that runs on MacOS X, Linux, and Windows.
I can compile a C# program using .NET on Windows, and then
take the .exe file, move it to Linux, and run it with the
mono JIT and libraries there -- tty slick!
They don't have the Windows Forms GUI up and running, so
I wouldn't use it for the main app, but for mostly calling
assemblies you define yourself (i e, your game), it seems
that .NET / Mono would be a nice environment. The Microsoft
development environment for .NET just cannot be beat -- in
the debugger, you step seamlessly between languages, can
look at any stack frame, inspect any variable, etc.
The con, though, is that the code for embedding/interfacing
between regular C/C++ and the CLR world is very different
between Mono and Microsoft. Rather, on the Microsoft side,
you'd want to use Managed C++ for your bridge, but on the
Mono side, there is no Managed C++ or mixed-mode assemblies,
so you use their CLR C-style API.
Cheers,
/ h+
|
