Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Virtual machine code)
(Virtual machine code)
Line 35: Line 35:
 
== Virtual machine code ==
 
== Virtual machine code ==
 
* [[ART (Android Runtime)]]
 
* [[ART (Android Runtime)]]
 +
* [[BEAM]] (Erlang)
 
* [[Bytecode]] (or p-code) — programs "compiled" into machine-independent code that loads or runs more quickly than raw interpreted source code; runs in an interpreter
 
* [[Bytecode]] (or p-code) — programs "compiled" into machine-independent code that loads or runs more quickly than raw interpreted source code; runs in an interpreter
 
* [[Dalvik Executable]] (DEX; virtual machine used in Android)
 
* [[Dalvik Executable]] (DEX; virtual machine used in Android)

Revision as of 01:43, 14 February 2015

File Format
Name Executables
Ontology

{{{caption}}}

Container formats for machine executable code. These often define different sections to be loaded into memory. Some formats may be compatible with different CPU architectures.

Contents

Directly executable

Shared libraries, chained files, etc.

(can't be run by themselves, but are used at runtime by other executables)

Virtual machine code

See also

See also Source code for code in a higher-level programming language that needs to be compiled, assembled, or interpreted, and Development for other files used in the development process, including object and library files that get linked into a finished executable. See Archiving for some forms of self-extracting archives and installer packages.

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox