51–60 of 64 posts
Earlier quoted context omitted.
Linq, which was inspired by ... Haskell! Would it be irresponsible to speculate that this article is directly responsible for the inclusion of Linq in C#? It would be irresponsible not to speculate!
LINQ was introduced by Erik Meijer, an Haskell researcher working on .NET team. http://research.microsoft.com/en-us/um/people/emeijer/papers...
Earlier quoted context omitted.
What event-handling semantics?
Responding to messages or choosing not to is event handling.
If anything, it introduces unnecessary semantics to syntactically distinguish between messages that are responded to with instance variables and messages that are responded to with function calls.
> The fact is that functional idioms work badly in languages that don't have syntactic support for them. You can even remove functional from the sentence. Powerful features of languages like Python and Lisp don't get you more power than languages like Java. They give you more power per unit of effort.
Wow, this is the worst article I've seen on hacker news front page in a very long time. C# has a tremendous potential for functional programming. There's some features that make a pure functional style easier and prettier in haskell, but C# has plenty of potential. The title is total link bait. I clicked because I know there are things to write about - like pervasive nulls and mutable-by-default variables to begin wi…
Earlier quoted context omitted.
Responding to messages or choosing not to is event handling.
In a sense, but message passing is the basic concept of object-oriented programming. Choosing which messages to receive and respond to is defining an interface. If you don't want to do that, you just don't want an object-oriented list of strings. Maybe you just want a list of strings that lives in a struct with some function pointers and some syntactic sugar for calling those functions. And that's fine. But for those…
Earlier quoted context omitted.
In a sense, but message passing is the basic concept of object-oriented programming. Choosing which messages to receive and respond to is defining an interface. If you don't want to do that, you just don't want an object-oriented list of strings. Maybe you just want a list of strings that lives in a struct with some function pointers and some syntactic sugar for calling those functions. And that's fine. But for those…
[deleted]
Earlier quoted context omitted.
Using Select and Where makes perfect sense.
In SQL it does.
from http://msdn.microsoft.com/en-us/library/bb397926.aspx
"Language-Integrated Query (LINQ) is a set of features introduced in Visual Studio 2008 that extends powerful query capabilities to the language syntax of C# and Visual Basic. LINQ introduces standard, easily-learned patterns for querying and updating data, and the technology can be extended to support potentially any kind of data store. Visual Studio includes LINQ provider assemblies that enable the use of LINQ with .NET Framework collections, SQL Server databases, ADO.NET Datasets, and XML documents."