their sorry, but what you appointed that's the same having a singleton access in a shared lib, there are two different cases you want one instance per thread, or a multi thread instance shared by multi apps, there are still coders on earth which are able to handle it properly.
On Fri, May 4, 2012 at 10:28 AM, mm w <0xcafef...@gmail.com> wrote: > As far as I can see, using the static container call, I did not get > any downsides , sure we are right in our mind and not trying to do > inappropriate behaviors with a singleton pattern, things you described > into your article which mostly just appoints strange practices which > never pop'ed in right minds. > > morality: Animals have a purpose to live because they are not there > self-creators 8=D > > On Fri, May 4, 2012 at 10:07 AM, blake <blake.me...@gmail.com> wrote: >> Especially since this topic, apparently, recurs, I thought it might be >> worth a summary. >> >> http://portabledroid.wordpress.com/2012/05/04/singletons-in-android/ >> >> G. Blake Meike >> Marakana >> >> The second edition of Programming Android is now on-line: >> http://shop.oreilly.com/product/0636920023005.do >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
