Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A few reasons for C++/CLI:</p> <ul> <li>it allows integration/mixing of managed and unmanaged code at a much finer level than other .NET languages</li> <li>Managed C++ wasn't particularly successful; C++/CLI was an attempt to make the .NET paradigm fit in better with existing C++ idioms</li> <li>While I don't think anyone thought it would overtake C# in popularity, I imagine that there were people who thought it would have a higher level of success than it has. Then again, for all I know it's very successful. I haven't done anything except toy stuff with it - but when the <a href="http://blogs.msdn.com/vcblog" rel="nofollow noreferrer">Visual C++ Team Blog</a> indicated that <a href="http://blogs.msdn.com/vcblog/archive/2009/05/27/rebuilding-intellisense.aspx#9644735" rel="nofollow noreferrer">VS2010 wouldn't have IntelliSense for C++/CLI</a> there was a bit of a firestorm of push-back. Much more than I expected (I'm not sure what MS expected).</li> </ul> <p>Microsoft did do some things in C++/CLI that I think are interesting even if you have no interest in .NET: the way they handled adding new keywords in a way that would least impact existing C++</p> <ul> <li>multi-word (or 'spaced') keywords (I think this technique is patented or patent-pending by Microsoft)</li> <li>contextual keywords</li> <li>'namespaced' keywords</li> </ul> <p>See <a href="http://blogs.msdn.com/hsutter/archive/2003/11/23/53519.aspx" rel="nofollow noreferrer">Sutter's article</a> for more details.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload