Browse by Tags

• To fight my fire I need a MOP

  I feel like I have reached a peak, I understand and use Inheritance, Polymorphism, Abstraction, Encapsulation and Parametric Inheritance (Generics) every day. They solve my computing needs but I very often I can think of better approaches to a problem and wish the compiler and CLI were not without limits. Generic covariance and contra-variance I have covered before so I'll jump right into something else I'd like to see. Meta Objects and Protocols - Jeremy mentioned this before and I agree but rather than bending to my will the objects defining interface I also want to work with the object systems very own protocol interface, I want MOP... MOP (Meta Object Protocols) the Protocols of the OOP system, how Inheritance, Polymorphism, Abstraction, Encapsulation are all defined and expressed in your language. With MOP you can change all of those, picking on inheritance, how and what you inherit and if you so wish change that. So why change that? Suppose I want to have multiple class inheritance? Read More... Posted Monday, September 08, 2008 1:17 PM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Silverlight PAL

  I started pondering about the DLR and running it on the SSCLI when I came across this article on the CoreCL R (shared source version of that would be fun) and the following. A lot of the Silverlight PAL benefits from lessons learned when we developed the Shared Source Common Language Infrastructure (SSCLI), also known as Rotor. The SSCLI ran on a number of UNIX-style platforms as well as Windows. The base OS functionality varies widely on UNIX-style platforms. The SSCLI PAL had to work on both microkernels (such as the Mach kernel in Mac OS X) and monolithic kernels and had to cope with different OS services such as threading, exception handling, and networking stacks. Because Silverlight only targets Windows and Intel Mac machines we were able to write Mac-specific implementations for many of the functions in the PAL, which helps with the size and performance of the PAL. The diagram in the article makes more sense but the CoreCLR Platform Adaption Layer (PAL) works in the same way as Rotors Read More... Posted Thursday, August 21, 2008 8:18 AM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Rotor 2.0 referance book

  The SSCLI aka Rotor tends to not draw all that much attention unless your a researcher or CLR wonk but it is one of (if not the best) source code referances to the very depths of .NET that you will ever find. For me personally getting the very most of the framemwork I develop on every day is about expanding my understanding of how that framework works, sure the compilers and there tricks come next but the root is the CLI. To top it all you can compile the CLR man !!! Therefore it fills me with joy that Joel has the news that along with Ted (da ThoughtWorker) Neward they have re-worked the SSCLI referance book to match the SSCLI 2.0 release. Ted wrote the first draft and Joel brings his experince as a former PM on the CLR team to this edition and it is great to see. An early draft in full is available here. I'm pleased as punch about this as I used it along side books such as CLR via C# and Customizing the CLR .if you after more CLR books then I have an old (from 2003) list here . Read More... Posted Thursday, August 21, 2008 7:38 AM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Vote for generic co\contra generic variance

  Back in 2006 I wrote about the co\contra variance generics support in .NET , fast foward to today and with the last few .NET releases not effecting the CLR this is still missing. I have high hopes the next version will bring some changes to the CLR and to ensure that this happens the change report needs some votes, add yours to parent bug here . Read More... Posted Tuesday, February 26, 2008 6:59 AM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Debugging with source

  Mike Taullty has a post on debugging your app's and needing to see source using a combination of debugger and reflector. Although things do differ one approach is to use Rotor , it really does depend on what your doing as to see if Rotor would be a good choice as a it is a limited sub-set of the .NET Framework after all. Rotor will let you run your app's under it's CLR and you can append a debugger like sos to it (and you can read the source files directly). Share this post: Email it! | bookmark it! | digg it! | reddit! Read More... Posted Thursday, October 26, 2006 12:52 PM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Phoenix rising

  For all you hardcore CLR nutters I ran across a download for the Phoenix project on Microsoft Connect. Read More... Posted Tuesday, August 01, 2006 11:40 AM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Mono's new GC

  I noticed that the latest Mono release has details on the new Mono GC . This is diffent to the current Read More... Posted Monday, July 10, 2006 10:06 AM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor

• Browse Rotor in VS

  Check this post , I agree that this is super useful for browsing the source. Read More... Posted Wednesday, June 07, 2006 4:48 PM from Andrew Stopford's Weblog | 0 Comments Filed under: .NET, CLR & Rotor