Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Virtual machine code: I'm not sure how we should index bytecode formats, it's too inconsistent as it is)
(Virtual machine code: Moved from Development)
Line 54: Line 54:
 
* [[Lingo bytecode]]
 
* [[Lingo bytecode]]
 
* [[Olive]] (executable archive embedding a virtual machine emulating original environment)
 
* [[Olive]] (executable archive embedding a virtual machine emulating original environment)
 +
* [[PYC]] ([[Python]] bytecode)
 
* [[Universal Machine (ICFP programming contest 2006)]]
 
* [[Universal Machine (ICFP programming contest 2006)]]
 
* [[WebAssembly]]
 
* [[WebAssembly]]

Revision as of 11:22, 11 June 2017

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)

Resource data used by executables and sometimes embedded in them

See Resources.

Meta-info files used in execution of programs/packages

Virtual machine code

(see Wikipedia:UVC-based preservation for use of virtual machines in archival preservation)

Macros or automated scripting

For additional formats, see Programming Languages.

Executable compression

See also Wikipedia:Executable compression.

See also

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox