﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Jeff Brown commented on Linq: Possibilities</title><description>I really was just referring to control flow in the example you had provided.  Expression trees do expose a lot more interesting internal structure which makes things like Linq possible.  I'm looking forward to using them for MbUnit v3.
  
  
You example is cute but I don't think it's a good use of lambda expressions since it makes too many assumptions about the form the expression provided.  What if I handed it something that did not include a method call?  The syntax may be convenient but the representation makes it unclear what behavior is anticipated.  I'll grant that this has a lot to do with the simplicity of the Load() and Save() methods presented for the purposes of the example.
  
  
At the same time, I'm irritated that lambda expressions are not really usable for user-defined control structures, they are not serializable, and they cannot be used as constant expressions in attribute declarations.  It would be nice if C# provided more closure in terms of its language contructs.  It's like the using statement in that way.  Lots of potential but ultimately very limiting.
  
  
Pet peeve: I can use numeric and string constants in switch statements but not other value types even though the compiler does generate a hashtable based dispatch mechanism for strings.  Is it trying to protect me from myself?
</description><link>http://ayende.com/2233/linq-possibilities#comment2</link><guid>http://ayende.com/2233/linq-possibilities#comment2</guid><pubDate>Thu, 22 Mar 2007 07:02:28 GMT</pubDate></item><item><title>Richard LOPES commented on Linq: Possibilities</title><description>Hi,
  
  
This is incredibly clever !
  
I see a lot of opportunities with such constructs.
  
Linq is going to change the way we code in C#.
  
  
By the way, your work on Linq for NHibernate doesn't go unnoticed. Excitement is growing about your work as an alternative to Linq + the MS OR/M.
  
  
Here is a link from a very regarded French blog:
  
http://www.dotnetguru.org/modules.php?op=modload&amp;name=News&amp;file=article&amp;sid=907
  
  
Thanks.
  
</description><link>http://ayende.com/2233/linq-possibilities#comment1</link><guid>http://ayende.com/2233/linq-possibilities#comment1</guid><pubDate>Mon, 19 Mar 2007 22:01:22 GMT</pubDate></item></channel></rss>