Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Meta-info files used in execution of programs/packages)
(Virtual machine code)
Line 45: Line 45:
 
* [[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)
 +
* [[Olive]] (executable archive embedding a virtual machine emulating original environment)
 
* [[Universal Machine (ICFP programming contest 2006)]]
 
* [[Universal Machine (ICFP programming contest 2006)]]
 
* [[Z-code]]
 
* [[Z-code]]

Revision as of 19:08, 3 May 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)

Meta-info files used in execution of programs/packages

Virtual machine code

Macros or automated scripting

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