I agree it may be dirty and icky, but its presumptuous to state that "You should "absolutely *should not* be doing this." There are many real-world situations where a program must be exited imediately or this call would not have been made available in the Android API. Perhaps you all don't remember the programmer that got sued for a bug that killed a patient with too much radiation because he didn't stop the program. There are many other non life-threatening cases where the right thing to do is to just halt the program. What would you do if you had zombie-game that users start running on some really slow devices and the frame-rate grinds down to 2 fps and your zombies look, well too dead, and then your app starts getting really bad ratings???
On Friday, May 25, 2012 12:08:48 AM UTC-6, Kristopher Micinski wrote: > > Because it's dirty, kills resources, goes against the application > lifecycle, is a dangerous way of destroying things without finalizing > things first, ... basically, for the same reasons you don't want to > unplug your machine while it's running... > > kris > > On Fri, May 25, 2012 at 1:47 AM, Yan wrote: > > Why? > > > > On May 21, 10:07 am, Kristopher Micinski > > wrote: > >> On Mon, May 21, 2012 at 9:45 AM, Yan wrote: > >> > An easier but less graceful way is just to System.exit(0) in the > >> > onPause then start from scratch every time... > >> > >> You absolutely *should not* be doing this. > >> > >> kris > > -- 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
