<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Arial, sans-serif" size="2">
<div> </div>
<div>Today we’re excited to announce the release of the Dynamic Language Runtime (DLR) as a separate Codeplex project. This release is a beta because we want our v0.9 to be the same sources and bits as IronPython v2.0. Due to a couple of good customer bugs,
they wanted to release v2 RC2 in NOV and hopefully RTW v2 in DEC.</div>
<div> </div>
<div>The DLR project provides one-stop shopping for folks who want to:</div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>implement a language on .NET using the DLR</li><li>add dynamic features to their existing language like C#’s ‘dynamic’ (<a href="http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=csharpfuture&DownloadId=3550"><font color="#0000FF"><u>http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=csharpfuture&DownloadId=3550</u></font></a>
)</li><li>add scripting to their applications.</li><li>create .NET libraries with dynamic objects</li></ul>
<div>This Codeplex project includes the DLR sources as well as sources for IronPython, IronRuby, and samples (such as ToyScript). This is a classic open source version 0.9 release with high quality code through much of the system. We’re shipping some of this
in the .NET 4.0 release coming up. Some parts are still open to design changes as we solidify those parts for post .NET 4.0, and we’ll continue to add more docs and samples. We will have coordinated releases or sync points across IronPython and IronRuby
sites for major releases so that if you’re not pulling from the DLR project, you can still see which sources or releases are consistent across our projects.</div>
<div> </div>
<div>Jim Hugunin did a great talk at PDC 08 on DLR architecture, concepts, and coding with the .NET 4.0 functionality (<a href="http://channel9.msdn.com/pdc2008/TL10/"><font color="#0000FF"><u>http://channel9.msdn.com/pdc2008/TL10/</u></font></a> ). In his
talk, he also outlines what’s in .NET 4.0:</div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>fast dynamic dispatch with polymorphic inline caching</li><li>dynamic object interoperability across languages and libraries (including C# ‘dynamic’ consuming IronPython and IronRuby objects naturally, including any language whose objects participate in the DLR’s dynamic object protocol)</li><li>support for library authors to easily make their model objects consumable with nice looking and lightweight code in languages that support the DLR dynamic object protocol (for example, with C#’s ‘dynamic’, you can write xml.Customer.Name instead of xml.GetChild(“Customer”).GetChild(“Name”)</li><li>ability to mix binding logic from various languages and library objects in a single dynamic call site cache</li><li>Expression Trees v2 with support for control flow, assignments, etc.</li><li>COM IDispatch binding as DLR dynamic objects</li></ul>
<div>The following highlights the support shipping only on Codeplex until a future .NET release:</div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>common hosting model for languages built on or supporting the DLR hosting model</li><li>helpers such as a default .NET binder, complex numbers, tuples</li><li>more Expression Tree support, such as globals access in hosted scenarios and iterator/generator functions.</li></ul>
<div> </div>
<div>All the code is available for what the DLR Team is shipping in .NET 4.0. Furthermore, we’re releasing all the code for LINQ Expression Trees v1 since the DLR merged its ASTs with LINQ trees. Some of you have noticed this code has been on the IronPython
site for a couple of months now. We will continue indefinitely shipping all of our code open source through .NET 4.0 shipping and future releases of .NET as we move more and more of the DLR into .NET (for example, the common hosting APIs and language implementer
APIs). We have no plan in place at this time for source take back from the community.</div>
<div> </div>
<div>It is worth noting that the sources and binaries in the .zip files are circa mid-October, and the daily source tree pushes have several small but pervasive cleanups to the API (name changes), perf improvements, and so on. We’re busy here solidifying final
design changes for the DLR parts going into .NET 4.0. We wanted to have our release match IronPython 2.0, and they had to lock down sources before we did. The documents in the release speak to the latest sources. Some of the documents are our internal working
specs, but in general we prefer you know where we’re planning to end up with the code. There are no significant cognitive changes in the APIs, so you’ll easily map from the docs to the actual code.</div>
<div> </div>
<div>For a consistent IronPython release, go to <a href="http://www.codeplex.com/ironpython"><font color="#0000FF"><u>www.codeplex.com/ironpython</u></font></a> and get their v2.0 RC2. We won’t normally have consistent release across all projects for RCs,
betas, etc., and we don’t have one for IronRuby today. When we RTW IPy v2 and DLR v0.9 shortly, we’ll have consistent releases for all three projects.</div>
<div> </div>
<div>If you want to read some documents without downloading sources or bits, go to <a href="http://www.codeplex.com/dlr/Wiki/View.aspx?title=Docs%20and%20specs"><font color="#0000FF"><u>http://www.codeplex.com/dlr/Wiki/View.aspx?title=Docs%20and%20specs</u></font></a>
:</div>
<ul style="margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<li>dlr-overview.doc</li><li>sites-binders-dyn-objs-spec.doc</li><li>expr-tree-spec.doc</li><li>dlr-spec-hosting.doc</li></ul>
<div> </div>
<div>There is a discussion list at <a href="http://www.codeplex.com/dlr/Thread/List.aspx"><font color="#0000FF"><u>http://www.codeplex.com/dlr/Thread/List.aspx</u></font></a> (click on the “get email notifications” link). All mail there goes to <a href="mailto:dlr@microsoft.com"><font color="#0000FF"><u>dlr@microsoft.com</u></font></a>
which has all the folks working on the DLR and our languages on it.</div>
<div> </div>
<div>Thanks,</div>
<div>Bill</div>
<div> </div>
<div> </div>
</font>
</body>
</html>