.NET framework lib source code available
-
hopefully it's easier to understand than the CRT or STL source !
-
hopefully it's easier to understand than the CRT or STL source !
Chris Losinger wrote:
hopefully it's easier to understand
I think the nature of C# will enforce that in some part. Of course, one can still write poorly designed code that's hard to decipher in any language. :) /ravi
My new year resolution: 2048 x 1536 Home | Music | Articles | Freeware ravib(at)ravib(dot)com
-
Chris Losinger wrote:
hopefully it's easier to understand
I think the nature of C# will enforce that in some part. Of course, one can still write poorly designed code that's hard to decipher in any language. :) /ravi
My new year resolution: 2048 x 1536 Home | Music | Articles | Freeware ravib(at)ravib(dot)com
i've seen plenty of hard-to-understand C#: just overdoing the OO and getting all happy with the interfaces is enough. in my opinion, if it takes more than 5 function calls to get to the first code that does anything, it's hard to understand.
-
-
Anyone try it yet? I'm downloading the QFE now, but half-expect to see a "just kidding - coming soon for reals this time!!" when it loads... :rolleyes:
Yes! I tried that long time back. I had access to the source during the beta test period. However, it is not as helpful as I expected it to be. For one some of the libraries are missing (aka LINQ, System.Configuration). Also because the code is highly optimized it is almost impossible to make out the variable values. In short, it is not as good as I expected it to be.
You have, what I would term, a very formal turn of phrase not seen in these isles since the old King passed from this world to the next. martin_hughes on VDK
-
Yes! I tried that long time back. I had access to the source during the beta test period. However, it is not as helpful as I expected it to be. For one some of the libraries are missing (aka LINQ, System.Configuration). Also because the code is highly optimized it is almost impossible to make out the variable values. In short, it is not as good as I expected it to be.
You have, what I would term, a very formal turn of phrase not seen in these isles since the old King passed from this world to the next. martin_hughes on VDK
-
Rama Krishna Vavilala wrote:
Also because the code is highly optimized it is almost impossible to make out the variable values.
That's a real shame. :(
1. Open a Visual Studio command prompt. 2. Type "set complus_zapdisable=1" to disable JIT optimization. 3. Type "devenv" to launch Visual Studio. 4. Open your solution. 5. Right-click on your project and hit Properties. 6. Navigate to the Debug tab. 7. Uncheck the "Enable the Visual Studio hosting process" checkbox. 8. JIT optimizations are now fully disabled when you go to debug. You can verify this by noting that in the Modules window, every entry in the Optimized column is No. Happy debugging! :)
-
1. Open a Visual Studio command prompt. 2. Type "set complus_zapdisable=1" to disable JIT optimization. 3. Type "devenv" to launch Visual Studio. 4. Open your solution. 5. Right-click on your project and hit Properties. 6. Navigate to the Debug tab. 7. Uncheck the "Enable the Visual Studio hosting process" checkbox. 8. JIT optimizations are now fully disabled when you go to debug. You can verify this by noting that in the Modules window, every entry in the Optimized column is No. Happy debugging! :)
-
1. Open a Visual Studio command prompt. 2. Type "set complus_zapdisable=1" to disable JIT optimization. 3. Type "devenv" to launch Visual Studio. 4. Open your solution. 5. Right-click on your project and hit Properties. 6. Navigate to the Debug tab. 7. Uncheck the "Enable the Visual Studio hosting process" checkbox. 8. JIT optimizations are now fully disabled when you go to debug. You can verify this by noting that in the Modules window, every entry in the Optimized column is No. Happy debugging! :)
Vega02 - You should go post this to .NET Tip of the Day[^] Those are handy settings ... :) D.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL