Comments on: Lambda in C#: Conciseness v Readability http://www.markhneedham.com/blog/2008/11/24/c-new-language-features-conciseness-v-readability/ Thoughts on Software Development Thu, 18 Mar 2010 23:35:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Richard http://www.markhneedham.com/blog/2008/11/24/c-new-language-features-conciseness-v-readability/comment-page-1/#comment-1650 Richard Fri, 28 Nov 2008 08:47:58 +0000 http://www.markhneedham.com/blog/?p=652#comment-1650 While I know it's a contrived example to make what I'd consider a valid point (and which I agree with), variable naming isn't helping with the readability either in this case - var fooStrings = foos.Select(foo => foo.ToString()); has a lot more chance of being understood by the unfamiliar than the slightly daunting algebraic feel of the single letter variables. I've always used => as a general "Go from this to that" sign in my notes so found it relatively straightforward to pick up. While I know it's a contrived example to make what I'd consider a valid point (and which I agree with), variable naming isn't helping with the readability either in this case -

var fooStrings = foos.Select(foo => foo.ToString());

has a lot more chance of being understood by the unfamiliar than the slightly daunting algebraic feel of the single letter variables. I've always used => as a general "Go from this to that" sign in my notes so found it relatively straightforward to pick up.

]]> By: Nate http://www.markhneedham.com/blog/2008/11/24/c-new-language-features-conciseness-v-readability/comment-page-1/#comment-1584 Nate Mon, 24 Nov 2008 18:04:24 +0000 http://www.markhneedham.com/blog/?p=652#comment-1584 Whoops, posted too quickly and didn't convert to the same output as you. My point still stands though. I tend to push usages internal to another object as I find that in addition to the readability problems (I was looking at the lambda version when I wrote the code to convert it to a string -- didn't read it properly), duplication also creeps out from these kinds of statements. Whoops, posted too quickly and didn't convert to the same output as you. My point still stands though. I tend to push usages internal to another object as I find that in addition to the readability problems (I was looking at the lambda version when I wrote the code to convert it to a string — didn't read it properly), duplication also creeps out from these kinds of statements.

]]> By: Nate http://www.markhneedham.com/blog/2008/11/24/c-new-language-features-conciseness-v-readability/comment-page-1/#comment-1582 Nate Mon, 24 Nov 2008 17:53:25 +0000 http://www.markhneedham.com/blog/?p=652#comment-1582 var foos = Foos.with(new Foo("bar1", "baz1"), new Foo("bar2", "baz2")); var fooString = foos.ToString(); var foos = Foos.with(new Foo("bar1″, "baz1″), new Foo("bar2″, "baz2″));
var fooString = foos.ToString();

]]> By: Scott http://www.markhneedham.com/blog/2008/11/24/c-new-language-features-conciseness-v-readability/comment-page-1/#comment-1579 Scott Mon, 24 Nov 2008 16:08:04 +0000 http://www.markhneedham.com/blog/?p=652#comment-1579 Agreed! I also find it useful to define custom LINQ operatorw that will simplify the expression required. Join, for example, is a tedious operator to use because it requires three expression. http://odetocode.com/Blogs/scott/archive/2008/11/16/12343.aspx Agreed! I also find it useful to define custom LINQ operatorw that will simplify the expression required. Join, for example, is a tedious operator to use because it requires three expression. http://odetocode.com/Blogs/scott/archive/2008/11/16/12343.aspx

]]>