Differences between current version and previous revision of BinaryExecutable.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 5 | Last edited on Friday, September 17, 2004 5:42:00 am | by AristotlePagaltzis | |
Older page: | version 4 | Last edited on Wednesday, February 11, 2004 1:23:25 pm | by AristotlePagaltzis | Revert |
@@ -1,5 +1,5 @@
-A program which is already compiled into binary form. Some [
OperatingSystem]
s only distribute [Binary] executables of their applications and OperatingSystem. [Linux] and the [BSD] family distribute their SourceCode as well as their binary executables are are held in great esteem for this.
+A program which is already compiled into binary form. Some OperatingSystem~
s only distribute [Binary] executables of their applications and OperatingSystem. [Linux] and the [BSD] family distribute their SourceCode as well as their binary executables are are held in great esteem for this.
-Confusion arises when your program compiles to
a VirtualMachine or other intermediate code, such as java's
class files
. Then your program isn
't compiled to a "binary executable"
(because it
's
not directly executable), but it is
compiled, and the file it is compiled into is definately binary
, and you can execute it
with help of the VirtualMachine.
+Confusion arises when your [Compiler] targets
a VirtualMachine or other intermediate code. The common example is a [Java]
class file
. These aren
't BinaryExecutable~s
(because they
're
not directly executable), but they are
compiled, and definitely in a [Binary] format
, and you can execute the code
with the
help of the VirtualMachine.
See also [a.out], [COFF] and [ELF].