There have been plenty of complaints about INotifyPropertyChanged and how developers do not like using strings, etc. Last year several bloggers presented type-safe alternatives that used either reflection or lambda expressions. Many are quick to point out the poor performance (same for reflection). Unfortunately ‘poor performance’ says little about usefulness of an implementation. The performance needs to be quantified and compared against all implementations so that ‘poor’ can be put in perspective. Speed is not the only issue, as memory should be compared as well....
|
11
shouts |
|
|||
4 comments posted.
#1
http://grnemo.myopenid.com/
51 days, 22 hours, 41 minutes ago said:
There is a serious coding bug in the project. The reflection calls are executed 1.000.000 times instead of 1. The code presented is buggy. Look in Reflector the setter of Dummy Property in DummyLambdaViewModel. Furthermore the blogpost should have been named as Expression Trees vs ... ... and not lambdas - (FastFuncs) (thus more meta data manipulation).
I am writing here because comments are disabled in this blog
#2
KKerr
51 days, 21 hours, 7 minutes ago said:
I just enabled comments... sorry (too much spam). The tests are all run using a loop of 1,000,000 iterations. Thus, I do not see the bug. Could you please clarify?
#3
http://grnemo.myopenid.com/
51 days, 44 minutes ago said:
By buggy I meant that if you want to use lambdas in a hot loop you should consider the underlying stuff. The problem isn't located in lambdas. You can't just compare these 3 stuff in the same way. Sorry for my previous reaction. :):)
#4
jmix90
17 days, 22 hours, 1 minute ago said:
This article may interest u all : http://blog.lexique-du-net.com/index.php?post/2010/02/24/DependencyProperties-or-INotifyPropertyChanged