dido:public:ra:xapend:xapend.b_stds:defact:orcle:javavm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:orcle:javavm [2021/08/13 13:28] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:orcle:javavm [2021/11/09 15:40] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Oracle: The Java® Virtual Machine Specification JVM ===== | ===== Oracle: The Java® Virtual Machine Specification JVM ===== | ||
| - | [[dido:public:ra:xapend:xapend.b_stds:defact:orcle| return to Oracle de facto Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:orcle:start| return to Oracle de facto Standards ]] |
| <table> | <table> | ||
| Line 17: | Line 17: | ||
| : //The Java Virtual Machine is the cornerstone of the Java platform. It is the component of the technology responsible for its hardware- and [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]]-independence, the small size of its compiled code, and its ability to protect users from malicious programs.// | : //The Java Virtual Machine is the cornerstone of the Java platform. It is the component of the technology responsible for its hardware- and [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]]-independence, the small size of its compiled code, and its ability to protect users from malicious programs.// | ||
| - | : //The Java Virtual Machine is an abstract computing machine. Like a real computing machine, it has an instruction set and manipulates various memory areas at run time. It is reasonably common to implement a [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming language]] using a virtual machine; the best-known virtual machine may be the P-Code machine of UCSD Pascal.// | + | : //The Java Virtual Machine is an abstract computing machine. Like a real computing machine, it has an instruction set and manipulates various memory areas at run time. It is reasonably common to implement a [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming language]] using a [[dido:public:ra:xapend:xapend.a_glossary:v:vm|virtual machine]]; the best-known virtual machine may be the P-Code machine of UCSD Pascal.// |
| : //The first prototype implementation of the Java Virtual Machine, done at Sun Microsystems, Inc., emulated the Java Virtual Machine instruction set in software hosted by a handheld device that resembled a contemporary Personal Digital Assistant (PDA). [[dido:public:ra:xapend:xapend.a_glossary:o:oracle|Oracle's]] current implementations emulate the Java Virtual Machine on mobile, desktop and server devices, but the Java Virtual Machine does not assume any particular implementation technology, host hardware, or host operating system. It is not inherently interpreted, but can just as well be implemented by compiling its instruction set to that of a silicon [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]]. It may also be implemented in microcode or directly in silicon.// | : //The first prototype implementation of the Java Virtual Machine, done at Sun Microsystems, Inc., emulated the Java Virtual Machine instruction set in software hosted by a handheld device that resembled a contemporary Personal Digital Assistant (PDA). [[dido:public:ra:xapend:xapend.a_glossary:o:oracle|Oracle's]] current implementations emulate the Java Virtual Machine on mobile, desktop and server devices, but the Java Virtual Machine does not assume any particular implementation technology, host hardware, or host operating system. It is not inherently interpreted, but can just as well be implemented by compiling its instruction set to that of a silicon [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]]. It may also be implemented in microcode or directly in silicon.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/orcle/javavm.1628875680.txt.gz · Last modified: 2021/08/13 13:28 by murphy
