Microsoft's C++/CLI Spec Has an Identity Crisis
Andy Updegrove writes "Microsoft's submission of its XML Reference Schema to Ecma has gotten lots of attention in recent months, because Microsoft offered it to Ecma to try to neutralize Massachusetts' adoption of the OpenDocument Format (ODF) standard. But last week it's earlier submission of C++/CLI to Ecma was in the limelight when the U.K. representatives to ISO cried foul over (of all things) its name, which they said was confusingly, and inappropriately, similar to C++. Some think that there may be more afoot, including the potential for Microsoft to add proprietary extensions after ISO finally adopts the new standard under a different name. Either way, the C++/CLI experience represents an interesting dry run for what to expect as Microsoft pushes the XML Reference Schema throught the same process."
..as Microsoft pushes the XML Reference Schema throught the same process.
thought + through = throught != a well perused article summary.
I thought C++ programs by default were CLI (as opposed to GUI).
'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
BadAnalogyGuy
:)
"This doesn't seem to be anything more than someone who's got his panties in a bunch about Microsoft"
I actually think that's a pretty good analogy
I actually think that's a pretty good analogy
Dammit!
Just name it --C/CLI :)
DYWYPI?
I'm dating myself
Yes... most of us call that "single".
And I don't recall in which C compiler I first saw support for the end-of-line comment "//" (Vax C?), but is sure as hell was non-standard at the time. I don't recall any pulling of hair and renting of garments over that.
You don't? Obviously you've never read comp.lang.c.
"Standards are there to reduce confusion, not to contribute to it"
Apparently ISO didn't get that memo:
Kilobyte