On Jan 28, 5:44 pm, David Turner <[email protected]> wrote: > On Thu, Jan 28, 2010 at 11:20 AM, Matt Kanninen <[email protected]>wrote: > Actually, I would really prefer to *get* *rid* of the Cygwin dependency, > since it's > just a pain to install, has many weird edge cases we don't want to support, > and > the compiler built against it run like molasse.
AGREED > > I'd like Android 3.0's bionic to be way too strong to run on a G1. I'd > > like it to be a lot closer to standard Linux, just still better. > > > What do you mean exactly ? I'd like to be able run code written for Linux, on Android. > > I'd like it if my private static variables didn't unexpectedly become > > > null. > > > Would you care to be more specific about this ? Sometimes Android applications crash. Google might not admit this, but sometimes it's the platforms fault. Sometimes its the OEMs fault. Sometimes its the fault of an application you didn't write that is running a service. etc. Here is what seems to happen then. The user will see an error message. If you try to swallow this error bad things happen. All your variables will be cleared. And then the activity lifecycle will restart for the current Activity. How well does your code handle that? I recommend you write static variables to the file system, and use getters and setters. This also makes it a lot easier to get your native code and your java code to get along, I hope. My native code and my java code do not yet get along very well. I'm not much of a native developer. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
