andrew_esh: I'm not saying that anything is lost in keeping the same bytecodes. I'm just double-checking the wording. The "d" in "dex" stands for "Dalvik" so the bytecode format is part of Dalvik. That part of Dalvik isn't being replaced. I just want to make sure that I'm not misunderstanding what's going on, and that it's safe to say that ART retains something that belonged to Dalvik. No judgment being made here.
On Tuesday, October 7, 2014 9:04:43 AM UTC-4, andrew_esh wrote: > > Why does ART have to use different "specific bytecodes" in order to > "entirely replace Dalvik"? What need is there for the bytecodes to change? > Your headline seems to imply that an Android platform would have to keep a > copy of the Dalvik VM for those situations where the ART can't replace it. > Is that true? If Dalvik is not kept as part of the system and only ART > remains, what is lost? > > It seems to me that if ART is able to execute all the same bytecodes that > Dalvik did, nothing is lost, and ART is a complete replacement for Dalvik, > even though it uses the same bytecodes. Or am I missing something here? > >> >> -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
