C
Cholo Lennon
+1 to that. It is piece of cake to throw fine looking and portable C++
GUI together using Qt tools. It is not too hard to embed a GUI module
that is made with Qt into existing application that has most GUI made
with MFC.
One (pseudo-)issue that i have encountered is that Qt never destroys
some of its singletons so Visual Studio's debugger reports these as
leaked. It can be silenced by turning the leak-detection temporarily
off when the singletons are allocated. Other issue is that the amount
of tinkering that is needed to embed non-Microsoft tools into VS IDE
is growing from version to version. IDE that is losing ability to
integrate tools? Other, well-known free and open source IDEs may pass
Visual Studio that way.
C++/CLI don't look at, it is very sad monster language. The Microsoft
tools often hide that it is C++/CLI and call it "C++ with managed
extensions enabled" and other such nonsense. That makes C++/CLI a good
tool for discrediting C++.
I don't agree. C++/CLI is a very good tool (in contrast with the
old/deprecated "Managed C++") to migrate code from native C++ to .Net
universe.
C++ is fine, platform neutral language and
has nothing to do with C++/CLI.
Yeah, C++/CLI is not C++. They are distinct languages, but they have a
lot of things in common.
Take C# when you target .Net as
platform, it wins C++/CLI in all aspects.
Not in all aspects. If someone needs a bridge between native and managed
world, C++/CLI is by far the best option. Also C++/CLI has a better
compiler than C#.
Regards