<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Yup, we still need to tackle attributes. Attributes are tricky
to fit into a dynamic language. It can be done, but it definitely has issues.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Another approach is to have attribute-based features exposed via
other mechanisms as well (for eg. an imperative API). Dynamic languages could
then build libraries on top of those APIs that worked well with the paradigms
of that particular dynamic language.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Given the existing set of attribute-based features, we will have
to think about this more. In the meantime, there is a workaround of using a
statically typed language just for the part which requires attributes.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
ironruby-core-bounces@rubyforge.org
[mailto:ironruby-core-bounces@rubyforge.org] <b>On Behalf Of </b>Curt
Hagenlocher<br>
<b>Sent:</b> Tuesday, February 05, 2008 2:58 PM<br>
<b>To:</b> ironruby-core@rubyforge.org<br>
<b>Subject:</b> Re: [Ironruby-core] Access from static languages<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>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.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Did I mention that this is
really really cool? :)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Feb 5, 2008 2:30 PM, Shri Borde <<a
href="mailto:Shri.Borde@microsoft.com">Shri.Borde@microsoft.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>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><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>