Yes, it's on purpose. Acquiring an element never fails, the limit just indicates how many objects are kept alive in the pool.
On Mon, Jan 9, 2012 at 8:12 PM, eihero <[email protected]> wrote: > Mr. Guy, > Thanks for your information. I had looked the related code and I found the > implementation of Pools.finitePool might acquire more elements than the > limit we set for it, if we successively acquire elements without releasing > them. Is this design purposely? Thanks. =) > > -- > 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 -- Romain Guy Android framework engineer [email protected] -- 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
