Comment Feed for Microsoft .NET Framework: CLR Futures (pdc2008 on Channel 9)

Re: Microsoft .NET Framework: CLR Futures

wellMS — Fri, 06 Nov 2009 08:45:02 GMT

I really like to hear some good news about improvements of JITed code quality

Buy high quality wholesale men watches

wholesale watches

Re: Microsoft .NET Framework: CLR Futures

iolanda256gmail — Tue, 20 Oct 2009 06:34:07 GMT

Yet cannot tiffany sale,Be together,The furthest distance in the worldbreitling

replica watch

Re: Microsoft .NET Framework: CLR Futures

Bent Rasmussen — Mon, 03 Nov 2008 23:50:30 GMT

The Design-by-Contract (CodeContract) is of course very Eiffelike, even the old-value semantics is there. The syntax is quite bloated in comparison [as leriksen71 says], but having the semantics at all is a first step. Also, tail recursion optimization is a welcome improvement.

Re: Microsoft .NET Framework: CLR Futures

lynn eriksen — Fri, 31 Oct 2008 04:24:55 GMT

Are code comments derived from or any way related to spec #? Will there be language support or only the class/object level?

Re: Microsoft .NET Framework: CLR Futures

alexhe — Mon, 27 Oct 2008 20:36:15 GMT

I really like to hear some good news about improvements of JITed code quality, memory footprint. The reason I care about this is because one of my BubbleSort(Just swapping data between array elements) tests shows that .NET 3.5 sp1 is about 40% slower than its counterpart written in Java (JDK1.6 update10 with server GC enabled.)

I am sure there are a lot of areas .NET did superior job, but why this big gap here?

Re: Microsoft .NET Framework: CLR Futures

hillr — Thu, 09 Oct 2008 06:00:52 GMT

If I'm reading this right, finally having a way to generate useful minidumps for managed code will be a welcome addition.