On Mar 12, 10:01 pm, Dianne Hackborn <[email protected]> wrote:
> You'll need to cache this stuff yourself.  I really recommend avoiding
> reflection though for any performance critical things -- even if there is no
> time required for the class/methods lookup, you will still tend to spam a
> lot of temporary objects.  If you are going to use reflection, plan to spend
> a good amount of time optimizing that code to get it to perform well.

As I develop convention-based databinding, reflection is really
necessary.
Can we hope that reflection caching will be implemented in future
versions of davlik?

regards,

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to