you might use method declared variables to help with scope... if you know a variable is only used in the method, why declare public.. keep it in the method and let the method clean it up at the end.
On Fri, Jan 29, 2010 at 3:32 PM, Jason Proctor < jason.android.li...@gmail.com> wrote: > The only time you need to use it is when the variable is referenced by >> an anonymous inner class (the compiler will let you know). >> > > is this a documented feature of Java? seems like a bit of a hack override > of "final" to me. > > much nicer to use a class member, IMHO. > > -- > jason.vp.engineering.particle > > > -- > 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<android-developers%2bunsubscr...@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
