Stan Lippman On Version 2 Of Managed C++
Lansdowne writes "Stan Lippman, one of the founding fathers of C++ and currently a language architect at Microsoft, has prepared an exhaustive translation guide, comparing old Managed C++ to the revised CLI/.NET version of C++. According to Lippman, "There are a number of significant weaknesses in the original language design (Version 1), which we feel are corrected in the revised language design (Version 2).""
I think Mono doesn't even support the current Managed C++ version... only C# and VB.NET. There's mcs, the Mono C# compiler, and mbas, the Mono VB.NET compiler, but there's no Managed C++ compiler, and I think mcs can't compile C++ code...
Go hug some trees.
Why can't they just change their compiler to generate managed code? Why do they need to change the syntax of C++ at all? In the open source project I work on we use the Boehm garbage collector for C++. So the number one reason to use managed code, automatic memory management, is already available to us. .Net is not just about garbage collection. There are many other facets to consider, like properties, value objects, etc. And let's not forget that these enhancements allow you to use either GC or non-GC, depending on your needs.
managed C++ is so different to C++ that it's a different language.
what MS have done is invent 2 new languages, managed C++ and C#. one of them is ok, the other is an abomination.
They didn't need to invent managed C++, all the interopability could have been provided by some library helper classes and COM. I've never heard of an explanation for manC++, and never heard of a new project using it. to link up with existing C++ codebase it's used, but should have been done as a library, not a new language.
Stan Lippmann really should have known a lot better. maybe they wouldn't let him in the C# team and made him work on the C++ stuff. He's bright enough to know that he's wasting his time on this pointless bastard language.