Yes, that is what a static variable is. If that's not the behavior you want, don't use statics.
On Tue, Mar 3, 2009 at 12:52 AM, taneroffline <taneroffl...@googlemail.com>wrote: > > Static members and variables are not freshly initilialised when > subsequelntly booting my application. > It seems that these are hold somewhere for the entire process lifetime > of my app. > Disallocation in code sometimes fails(myObject = null; ). > > Has someone experienced the same ? What would be a good practise ? Any > Workaround? > > Thanks > taneroffline > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
