Dalvik respects some of the JVM's memory semantics. you cannot perform raw-pointer accesses with it for example. this means that compiling C/C++ to it is not generally feasible.

but you can envision writing C/C++ code that is called through JNI (useful for a lot of CPU-intensive stuff, while the App UI is still in Java and can use many Java services). and in Android, such a program crashing would only bring down its process, not the whole system.

On Mon, Mar 10, 2008 at 4:34 PM, Erik Martino <erik...@gmail.com <mailto:erik...@gmail.com>> wrote:

Another solution would be to create a C/C++ compiler that targets the dalvik VM. Then you would have tonnes of code ready to use that would still be platform independent and doesn't bring the phone down when it crashes.

On Mar 10, 1:43 am, sbVB <sbvi...@gmail.com <mailto:sbvi...@gmail.com>> wrote: > Hi, all > > For many reasons, Android MUST have a C/C++ SDK. > For instance: I have countess lines of code written in C++ and > wxWidgets; of course, I want to compile this to Android. Don't tell me > Java is better. > I'm focusing in reusing my code. > > I've spent many hours digging out the web, finding "hacker-like" > recipes to use native code on Android, as well as my own hours of > experimentation. > But that's not the way it should be. > > For the sake of Android, the Google development team must provide a > complete C/C++ SDK for Android, much similar of the one found in > Linux. > Development tools such as g++, make, ldconfig, ar, etc. should be > included in this C/C++ SDK for Android. > > If Google does not provide this C/C++ SDK, Android might get > discredited.