3 ms·
This one: http://www.amazon.com/Pro-LINQ-Language-Integrated-Query/dp/1430216441/ref=sr_1_1?ie=UTF8&s=books&qid=1277320215&sr=8-1 http://www.amazon.com/Pro-LINQ
by cabalamat 16y ago
This one: http://www.amazon.com/Pro-LINQ-Language-Integrated-Query/dp/1430216441/ref=sr_1_1?ie=UTF8&s=books&qid=1277320215&sr=8-1 http://www.amazon.com/Pro-LINQ-Language-Integrated-Query/dp/...
The example on page 3 was:
Dim greetings() As String = {"hello world", "hello LINQ", "hello Apress"}
Dim items = _
From s In greetings _
Where s.EndsWith("LINQ") _
Select s
Which In Smalltalk would be:
greetings := #('hello world', 'hello LINQ', 'hello Apress').
items := greetings select: [:s | s endsWith: 'LINQ'].
Needless to say I was not completely bowled over by this stunning Microsoft innovation.
- kenjackson 16y agoI don't think this one line is exactly where all the innovation is. But it is representative of getting your toe in the water. But this is the typical argument I hear from people about anything. "Hey, that was a good movie"... "Dude that plot is basically a derivative of Hamlet with a twist of Revelation, chapter 3. Nothing really new there". Or the most standard, "Actually you can do that with Lisp." I'm sure you probably know that everything in that Linq query is pure syntatic sugar. Not runtime changes needed. But with all that said, I'm sure MS didn't do this to be "innovative". At least I hope not. I assume they did it to make the lives of developers easier. That's the real test, not if no other language ever implemented the feature.
- cabalamat 16y ago> I assume they did it to make the lives of developers easier. I imagine you're right, and it's an entirely reasonable thing for MS to do. What I took exception to is the way the book spun it as an amazing new technology.
- kenjackson 16y agoI agree. The "has your world been shaken yet" (or whatever the line they use) was over the top. Unnecessary. For most users, the code speaks for itself.