<?xml version="1.0" encoding="UTF-8"?><item><title>The CLR and Dynamic Languages</title><description>&lt;P&gt;This &lt;A href="http://www.theserverside.net/news/thread.tss?thread_id=24878"&gt;article&lt;/A&gt; is a summary of IronPython, an implementation of a dynamic language (Python) on the CLR.&amp;nbsp; Basically it's been &amp;#8220;common knowlege&amp;#8221; that the CLR is not a good platform for dynamic languages (basically languages that make a lot of decisions at runtime instead of at compile time).&lt;/P&gt;&#13;
&lt;P&gt;The discovery is that the CLR is actually a pretty good platform for a dynamic language.&lt;/P&gt;&#13;
&lt;P&gt;This is good news since Monad (the new Microsoft Shell) has a scripting language that is (fairly simple) dynamic programming language, and knowing that we should be able to expect decent performance from those scripts is encouraging.&lt;/P&gt;&#13;
&lt;P&gt;(Monad lets you execute statements like:&lt;/P&gt;&#13;
&lt;P&gt;&amp;nbsp; $o = new-myobject&lt;BR&gt;&amp;nbsp; echo $o.Rows.Count&lt;/P&gt;&#13;
&lt;P&gt;And this is executed much like VBScript in that there is no compiler.. it's at runtime that the runtime has to figure out if $o has a Rows property, and if that property has a Count, etc..)&lt;/P&gt;&#13;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description><pubDate>Thu, 01 Sep 2005 19:17:07 GMT</pubDate></item>