nders). This, I think, is just plain beautiful.
From: [EMAIL PROTECTED] on behalf of Michael Latta
Sent: Tue 9/20/2005 9:47 AM
To: 'Discussion of IronPython'; [EMAIL PROTECTED]
Subject: RE: [IronPython] Extension methods...
Keith,
Your summary of LINQ is
20, 2005 12:47 PM
> To: 'Discussion of IronPython'; [EMAIL PROTECTED]
> Subject: RE: [IronPython] Extension methods...
>
> Keith,
> Your summary of LINQ is correct in technical details. I believe that the
> comment was about preferred syntax. The same could be done f
level something that is more "Pythonish" would be nice.
Michael
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Keith J. Farmer
Sent: Tuesday, September 20, 2005 9:38 AM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: RE: [IronPython]
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
om: [EMAIL PROTECTED] [mailto:users-
> [EMAIL PROTECTED] On Behalf Of Keith J. Farmer
> Sent: Monday, September 19, 2005 3:43 PM
> To: users-ironpython.com@lists.ironpython.com
> Subject: [IronPython] Extension methods...
>
> All the fun Linq bits run on beta 2. All that&#
All the fun Linq bits run on beta 2. All that's needed is a way to make use of
extension method attributes, which is remarkably Pythonic: foo.Bar(baz) ->
Gleep.Bar(foo, baz). Python already has lambdas, but could use a means to
generate expression trees rather than functions.
