I wasn't going to enter back into this discussion because it's one of those that polarises like checked Exceptions.
I also use singletons, but on a rare and very precise basis. And if you have mentored as many developers as I have then you will understand why the default mantra of don't use a singleton is valid. Junior developers seem to become infatuated with them, overuse them, lose all perspective of the OO nature of the language and start treating them as global functions. Encapsulation and responsibility go out the window. And on top of that you get all the attendant problems of objects with indefinite life spans. If you know what you are doing, fine. But it's similar to the mantra we give kids "don't run with scissors". William -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
