A preamble to MC++ conversion
First, my thanks to Sam Gentile for providing more trails to MC++ info. This note is more of a preamble to MC++ conversion and why MC++ is here to stay. The reality is that MS does cater a lot for their enterprise customers (wait till 'Yukon' gets here). The enterprise market (aka corporate) contains former UNIX customers who are moving into the MS .NET world and they bring with them hundreds of millions lines of C++ code. MS is making major inroads in the enterprise market ergo we will be seeing more C++ code. Development code contains libraries that are not easily converted - these may range from business logic, data structures & algorithms right down to utility and communications.
By my experience in developing for the financial services industry, a vast majority of this code is very performance sensitive. So I have to formulate some MC++ conversion strategies. Case in point - calling a DLL via the Platform Invoke has an overhead of up to 30 native X86 instructions per call. With more overhead if there is a need to marshal function arguments (varies based on parameter types).
Hmm...the next few months will keep me fairly occupied with MC++ and some new toys.