decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Didn't use bytecode? | 396 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Uses Dalvik executables
Authored by: Anonymous on Wednesday, April 25 2012 @ 05:56 AM EDT
.dex files instead.

[ Reply to This | Parent | # ]

Didn't use bytecode?
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 | # ]

Didn't use bytecode?
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 | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )