On Tue, Jul 20, 2010 at 2:20 PM, Sturla Molden <span dir="ltr">&lt;<a href="mailto:sturla@molden.no">sturla@molden.no</a>&gt;</span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


Microsoft&#39;s LINQ is also similar to your suggestion.<br>
   <br>
</blockquote>
</div><br>
LINQ is just to compensate for lack of duck-typing in C# ;-) Also when used to Pythons list comprehensions, LINQ syntax feels like thinking backwards (which can be quite annoying) :-(<font color="#888888"></font><br clear="all">

</blockquote></div><br>Well, LINQ has a bit more going on from what I can tell -- you can actually get at the expressions and work with them.  This is something NumPy and database abstraction layers both need, and they both currently use method override hacks that have certain limitations (e.g., you capture  ==, but you can&#39;t capture &quot;and&quot;).  If you work really hard you can decompile the bytecodes (DejaVu did this for lambdas, but not generator expressions).  I don&#39;t think  I&#39;ve even seen a language proposal that actually tries to tackle this though.<br>

<br>-- <br>Ian Bicking  |  <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>