Peter da Silva wrote:
THe most hateful thing about C++ is that it's so bad even Microsoft gave up on it
Did they? There's Managed C++ and C++/CLI. And AFAIK ATL is alive and kicking, too. Not to mention a teraton of legacy MFC and COM code. Of course they "encourage" people to switch to C# or VB .NET or whatever, but they "actively maintain" MFC (read: repeatedly break what sort of worked; for example, they *merged MFC with ATL*, so now class CString translates to two different instantiations of the same template depending on whether you link with MFC statically or dynamically, and if you use libraries that do *both*, you are royally screwed).
If C++ weren't so bad, it would have been Objective C or D or something. Which could have saved many a head a long series of meetings with the wall. But would that affect C#? Isn't the point of C# to be the "native/systems programming language" of .NET, and isn't the point of .NET to clone the JVM (which isn't completely open and has no completely open alternative I know of which Microsoft could use/abuse instead of rolling their own)? AFAIK Objective+C and char(int('C')+1) are not supposed to run in JVM-style managed environments any more than C.operator++(int) or C itself are.
