If you needed it, you'd be using it. I wrote a test program where I duplicated (not ported) a portion of my 2-D geometry library in C#. Test consisted of finding all the intersections in a list 100,000 arbitrary polygons of between 7 and 15 corners. My first run came in at 7 times slower than my C++ code. After reading about optimization techniques and doing my own tuning, I got it down to 2.5 times slower and was actually quite impressed. The problem was the tuning and optimizations made the code look like crap and any potential structural benefits went right out the window. Bottom line is, CLR is not great for finding polygonal intersections, but it does a bang-up job on many things I don't need. Use the tools for the job.

I removed the round power button from the front of my HP computer and installed a cigarette lighter there. It's not high speed or anything, just a normal one. My ashtray sits in the top CD tray. Now I just need to find room for a cooler. My software turns into to hardware.

Just imagine flipping it.

I don't even care if the ones work! Tight code? All the programs I've ever written reside in the same exe. Just randomly set eip in the image and it will run a program. When we gave Saddam chemical weapons, did we want him to use them?

If you've been programming long enough, you can read anything. That's why only beginners use lots of comments. Plus, comments have to be maintained too.