[Evolution in aciton] C#1.1=>2.0=>3.0 [Querying Collections]
If want filter out a price greater than $10 ,in the products. we need to loop around,testing each element and printing it out where appropriate.
Looping ,testing,printing out![]() C#1.1
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() The dependency is obvious because of the nesting. |
C#2.0 Lets us flatten things out a bit![]()
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
In particular, it makes it very easy to change the condition we're testing for and the aciton we take on each of the matchs independently. * The FindAll and ForEach methods in C#2.0 just help to encourage you to consider separation of concerns. |
So, we could have put all the testing and printing into one statment.[C#2.0]![]()
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
C#3.0 ![]() improves matters dramatically by removing a lot of the fluff surrounding the actual logic of the delegate.
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
So much For this!![]() |