http://blogs.msdn.com/mmaly/archive/2008/03/03/building-a-dlr-language-extension-methods.aspxIn the previous post we explored options to express dynamic behavior of "formatting" an object for output. First option was to use relatively well fitting dynamic operation from the DLR core set - CodeRepresentation. There's another option which we'llen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/mmaly/archive/2008/03/03/building-a-dlr-language-extension-methods.aspx#8035040Tue, 04 Mar 2008 23:59:17 GMT91d46819-8472-40ad-a661-2c78acb4018c:8035040onektwenty4<p>Whats the reasoning for making your extension methods the way you did instead of using the 'this' modifier in the methods? &nbsp;Are we just doing it this way to keep ToyScript simple?</p> http://blogs.msdn.com/mmaly/archive/2008/03/03/building-a-dlr-language-extension-methods.aspx#8056190Thu, 06 Mar 2008 00:47:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:8056190mmaly<p>Good question. The main reason is simply that IronPython and DLR currently only takes dependency on the Visual Studio 2005 version of the .NET runtime and compilers, which don't yet have the &quot;this&quot; modifier available. In the future it is obviously something we should support.</p>