Battle brewing over C++, .NET, and standards

As C++ is before the Ecma for standardization, there is a little problem.  Seems that tying it to the Common Language Infrastructure (CLI) ties it too closely to .NET WebProNews continues ...

There seems to be a C++ schism going right now as the Ecma consortium works out standards for the widespread programming language. The specification will bind C++ to the Common Language Infrastructure (CLI). This presents a problem for some because it ties the language a little too closely to .NET.

The basis of the controversy comes from the fact that .NET Framework is an integral part of the CLI standard. As ZDNet pointed out, it also paved the way for Microsoft to say that .NET was standards-compliant. They also pointed out one of the major strengths of .NET is the ability to write in a variety of languages. This isn't a bad thing.

But, ZDNet continues, the CLI really needs support from a "neutral motherload language" like C++. This would allow CLI to gain some clout and really move to the next level. This is the reason Ecma is tying C++ to CLI.

Times like this I long for BASIC ... okay not really.  Logo maybe ;-).

Tags: C++, .Net, CLI, Ecma