tag:blogger.com,1999:blog-7577421612120825312.post1145630802704876379..comments2011-05-16T15:48:44.746+01:00Samhttp://www.blogger.com/profile/01345100698738870730noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7577421612120825312.post-4557656539221127992011-05-16T15:48:45.466+01:002011-05-16T15:48:45.466+01:00I think this is beautiful. It already reminds me a lot of the ways you would handle input in Haskell. Just a minor note, it should be sufficient to write:<br>.Select(int.Parse), since the signature fits.Frank Quednauhttp://realfiction.net/noreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-54455798359011339512011-03-13T23:12:04.099Z2011-03-13T23:12:04.099ZI just independently invented a console application to dynamically compile and execute user-input LINQ query code. The user queries work over an IEnumerable&lt;string&gt; that is piped from Console.In to provide data input so that you can chain multiple tools together, much like how you&#39;ve done, but I&#39;ve made it generic and scriptable.<br /><br />Have a look: http://bittwiddlers.org/?p=141Jameshttp://www.blogger.com/profile/08275844908430699697noreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-12604281588600388422008-11-20T12:30:00.000Z2008-11-20T12:30:00.000ZDan,<BR/> Thanks for the feedback. I'm glad you found the article interesting. <BR/><BR/>I'll consider my wrist slapped with regards to the "no pun intended" :-). I don't recall using that phrase in any recent articles, and I'll try to keep it that way.<BR/><BR/>SamSamhttp://www.blogger.com/profile/01345100698738870730noreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-50109420916208813432008-11-20T11:02:00.000Z2008-11-20T11:02:00.000ZQuite quite interesting. It seems you can turn anything into LINQ coding and that's useful for my learning efforts.<BR/><BR/>One thing I wanted to tell you. It annoys me a bit when you use the 'no pun intended' thing in your writings. I mean, your style is nice and pleasant to read, but this little things simply bug me.<BR/>Detailed explanation (a bit too rude) of the annoyance here: http://www.thebestpageintheuniverse.net/c.cgi?u=punsDan Dumitrunoreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-91045499281083682042008-05-13T16:28:00.000+01:002008-05-13T16:28:00.000+01:00Thanks Frank!<BR/><BR/>That's a useful reminder about the Select statement. I guess I find the syntax I used slightly more readable since (to my eyes anyway) it conveys the fact that a transformation is happening to the lambda variableSamhttp://www.blogger.com/profile/01345100698738870730noreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-91205940960078705092008-05-13T15:54:00.000+01:002008-05-13T15:54:00.000+01:00I think this is beautiful. It already reminds me a lot of the ways you would handle input in Haskell. Just a minor note, it should be sufficient to write:<BR/>.Select(int.Parse), since the signature fits.Frank Quednauhttp://realfiction.net/noreply@blogger.comtag:blogger.com,1999:blog-7577421612120825312.post-16438459199497866042008-05-13T15:53:00.000+01:002008-05-13T15:53:00.000+01:00I think this is beautiful. It already reminds me a lot of the ways you would handle input in Haskell. Just a minor note, it should be sufficient to write:<BR/>.Select(int.Parse), since the signature fits.Frank Quednauhttp://realfiction.net/noreply@blogger.com