> With LINQ's expression trees, they seem to tackle the same problem as Lisp does with S-expressions. The problem is that at the moment, it's a lot harder to w

> With LINQ's expression trees, they seem to tackle the same problem as Lisp does with S-expressions. The problem is that at the moment, it's a lot harder to work with Linq expression trees than with S-Expressions. If you're not very, very, very careful, expression trees can very quickly become an unmaintainable, terrible mess and it is very hard to debug them - it's a lot more painful than in Lisp. This might change in the future though with better tools.