<div>While this is really cool, it doesn't (for instance) let you expose a dynamic object to WCF without manually wrapping it in a static C# class -- or any other CLR feature based on method, property or class-level attributes.</div>
<div> </div>
<div>Did I mention that this is really really cool? :)<br><br></div>
<div class="gmail_quote">On Feb 5, 2008 2:30 PM, Shri Borde <<a href="mailto:Shri.Borde@microsoft.com">Shri.Borde@microsoft.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">C# is looking into making it easy to talk with DLR objects. See <a href="http://blogs.msdn.com/charlie/archive/2008/01/25/future-focus.aspx" target="_blank">http://blogs.msdn.com/charlie/archive/2008/01/25/future-focus.aspx</a><br>
<br>-----Original Message-----<br>From: <a href="mailto:ironruby-core-bounces@rubyforge.org">ironruby-core-bounces@rubyforge.org</a> [mailto:<a href="mailto:ironruby-core-bounces@rubyforge.org">ironruby-core-bounces@rubyforge.org</a>] On Behalf Of Curt Hagenlocher<br>
Sent: Tuesday, February 05, 2008 12:43 PM<br>To: <a href="mailto:gakins@insomnia-consulting.org">gakins@insomnia-consulting.org</a>; <a href="mailto:ironruby-core@rubyforge.org">ironruby-core@rubyforge.org</a><br>Subject: Re: [Ironruby-core] The future of Ruby.NET<br>
<br>On Feb 5, 2008 12:31 PM, Greg Akins <<a href="mailto:angrygreg@gmail.com">angrygreg@gmail.com</a>> wrote:<br>><br>> Meaning, that like Ruby.Net can we write .Net classes in Ruby rather<br>> than writing them as strings that are passed to the RubyEngine?<br>
<br>There's a kind of mismatch between the capabilities of statically<br>defined types (as in the CLR) and the dynamic classes that Ruby<br>offers. What should happen to the corresponding CLR class if, for<br>instance, someone were to dynamically add methods to the Ruby class?<br>
CLR classes don't support that kind of operation.<br><br>The best option in this regard is probably to allow a dynamic (Ruby or<br>other DLR) class to be delegated to by a statically-defined wrapper.<br>Conceptually, such a wrapper could be automatically generated from the<br>
Ruby class definition, but once defined it would be unalterable.<br><br>--<br>Curt Hagenlocher<br><a href="mailto:curt@hagenlocher.org">curt@hagenlocher.org</a><br>_______________________________________________<br>Ironruby-core mailing list<br>
<a href="mailto:Ironruby-core@rubyforge.org">Ironruby-core@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" target="_blank">http://rubyforge.org/mailman/listinfo/ironruby-core</a><br>_______________________________________________<br>
Ironruby-core mailing list<br><a href="mailto:Ironruby-core@rubyforge.org">Ironruby-core@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" target="_blank">http://rubyforge.org/mailman/listinfo/ironruby-core</a><br>
</blockquote></div><br>