|
Authored by: Anonymous on Wednesday, April 25 2012 @ 05:56 AM EDT |
.dex files instead. [ Reply to This | Parent | # ]
|
|
Authored by: PJ on Wednesday, April 25 2012 @ 07:45 AM EDT |
So can you tell me, since you seem to know,
what exactly from the APIs gets shipped?
I read they are divided into two pieces,
one the simple command name and whatever that
side holds, and the other sounded like the
documentation. Do they both ship in a
finished product?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Wednesday, April 25 2012 @ 11:15 AM EDT |
Wikipedia
article about Dalvik has a short summary of differences between the Dalvik
VM and a traditional Java VM.
Technically Dalvik still uses "a bytecode
format" for its compiled programs. Its just not the same as the one used by
Java VMs. There's no one-to-one mapping either, its a different kind of
instruction set (register-based, not stack-based).
A programmer writing an
app for Android would run the "javac" compiler first (producing .class files,
which a regular Java VM would be able to directly run, if it had the proper
Android .class libraries to run them with) and then the "dx" translator tool
that converts the Java bytecode into the kind of bytecodes that Dalvik wants.
Its actually more of a "re-compiler"... it treats the Java bytecodes almost like
source code, and compiles them into a somewhat different kind of bytecode. [ Reply to This | Parent | # ]
|
|
|
|
|