Right.. it's just a pattern for metaprogramming. The current implementation
just has a little bit of compiler assist.
There are the underlying extension methods (which are defined in a very
Pythonic way: static Foo Bar(this Baz, Gleep)), which can be used directly, or
wrapped in sugar. Of c
Yes, Michael, preferred syntax was the point of the examples. Although this
may simply be a case of "I'm familiar with Python syntax and I'm not
familiar with LINQ", there is a greater similarity between the Python list
comprehension and SQL syntax. This makes it easy to jump between the SQL
data
Keith,
Your summary of LINQ is correct in technical details. I believe that the
comment was about preferred syntax. The same could be done for Python, by
allowing the list comprehension syntax to be used to produce expression
trees not just executable blocks. This was the main thing I liked abou
LINQ is *very* simple. It's simply, as Anders puts it, a pattern for
describing queries. It's made useful by way of extension methods and
the compiler deciding to convert a lambda expression not into a
delegate, but into an expression tree.
The query methods (Where, OrderBy, Select, etc) take tre
LINQ is pretty cool -- thanks for the update Keith.
I do find it amusing that many of these "queries" are available in standard
Python through list comprehensions, lambda, etc.
Here's a simple LINQ example:
[Category("Restriction Operators")]
[Title("Where - Simple 1")]
[Description("This sample
