Editing Bytecode (section)

==References==
{{reflist|refs=
<ref name="Jucs_Lua">{{cite web |url=http://www.jucs.org/jucs_11_7/the_implementation_of_lua/jucs_11_7_1159_1176_defigueiredo.html |title=The Implementation of Lua 5.0}} (NB. This involves a register-based virtual machine.)</ref>
<ref name="Dalvik">{{Cite web |url=http://source.android.com/tech/dalvik/dalvik-bytecode.html |title=Dalvik VM |url-status=dead |archive-url=https://web.archive.org/web/20130518021154/http://source.android.com/tech/dalvik/dalvik-bytecode.html |archive-date=2013-05-18 |access-date=2012-10-29}} (NB. This VM is register based.)</ref>
<ref name="Byte_Machine">{{cite web |title=Byte Code Vs Machine Code |website=www.allaboutcomputing.net |url=http://www.allaboutcomputing.net/2014/07/byte-code-vs-machine-code.html |access-date=2017-10-23}}</ref>
<ref name="Dynamic_Machine_Code">{{cite web |title=Dynamic Machine Code Generation |publisher=Google Inc. |url=https://chromium.googlesource.com/external/github.com/v8/v8.wiki/+/eb80fb157da30e8c838e758f178de674e47648ed/Design-Elements.md |access-date=2024-12-01  |archive-date=2017-03-05  |archive-url=https://web.archive.org/web/20170305155607/https://github.com/v8/v8/wiki/Design%20Elements |url-status=live }}</ref>
<ref name="Loitsch_Bytecode">{{Cite web |url=http://www.dartlang.org/articles/why-not-bytecode/ |title=Why Not a Bytecode VM? |last=Loitsch |first=Florian |publisher=[[Google]] |url-status=dead |archive-url=https://web.archive.org/web/20130512215811/http://www.dartlang.org/articles/why-not-bytecode/ |archive-date=2013-05-12}}</ref>
<ref name="Javascript">{{Cite web|url=https://2ality.com/2012/01/bytecode-myth.html|title=JavaScript myth: JavaScript needs a standard bytecode|website=2ality.com}}</ref>
<ref name="Arizona_Icom">{{Cite web |url=http://www.cs.arizona.edu/icon/ftp/doc/ib1up.pdf |title=The Implementation of the Icon Programming Language |url-status=dead |archive-url=https://web.archive.org/web/20160305123148/http://www.cs.arizona.edu/icon/ftp/doc/ib1up.pdf |archive-date=5 March 2016 |access-date=9 September 2011}}</ref>
<ref name="Icon_Unicon">{{Cite web|url=http://unicon.sourceforge.net/book/ib.pdf |archive-url=https://ghostarchive.org/archive/20221009/http://unicon.sourceforge.net/book/ib.pdf |archive-date=2022-10-09 |url-status=live|title=The Implementation of Icon and Unicon a Compendium}}</ref>
<ref name="Paul_2001_KEYBOARD">{{cite newsgroup |title=KEYBOARD.SYS internal structure |newsgroup=comp.os.msdos.programmer |author-first=Matthias R. |author-last=Paul |date=2001-12-30 |url=https://groups.google.com/d/msg/comp.os.msdos.programmer/l_IuSHsBDWQ/887rJF9IYmMJ |access-date=2016-09-17 |url-status=live |archive-url=https://archive.today/20170909082257/https://groups.google.com/forum/%23!msg/comp.os.msdos.programmer/l_IuSHsBDWQ/887rJF9IYmMJ |archive-date=2017-09-09 |quote=[…] In fact, the format is basically the same in [[MS-DOS]] 3.3&nbsp;- 8.0, [[PC&nbsp;DOS]] 3.3&nbsp;- 2000, including Russian, Lithuanian, Chinese and Japanese issues, as well as in Windows NT, 2000, and XP […]. There are minor differences and incompatibilities, but the general format has not changed over the years. […] Some of the data entries contain normal tables […] However, most entries contain ''executable code'' interpreted by some kind of [[p-code machine|p-code interpreter]] at *[[run time (program lifecycle phase)|runtime]]*, including conditional branches and the like. This is why the [[KEYB (DOS command)|KEYB]] driver has such a huge memory footprint compared to table-driven keyboard drivers which can be done in 3 - 4 Kb getting the same level of function except for the interpreter. […]}}</ref>
<ref name="Mendelson_2001_KEYBOARD">{{Cite web |url=http://www.columbia.edu/~em36/wpdos/eurodos.html |title=How to Display the Euro in MS-DOS and Windows DOS |last=Mendelson |first=Edward |author-link=Edward Mendelson |date=2001-07-20 |at=Display the euro symbol in full-screen MS-DOS (including Windows 95 or Windows 98 full-screen DOS) |url-status=live |archive-url=https://web.archive.org/web/20160917201248/http://www.columbia.edu/~em36/wpdos/eurodos.html |archive-date=2016-09-17 |access-date=2016-09-17 |quote=[…] Matthias [R.] Paul […] warns that the [[IBM PC DOS]] version of the keyboard driver uses some internal procedures that are not recognized by the [[Microsoft]] driver, so, if possible, you should use the [[IBM]] versions of both [[KEYB.COM]] and [[KEYBOARD.SYS]] instead of mixing Microsoft and IBM versions […]}} (NB. What is meant by "procedures" here are some additional bytecodes in the IBM KEYBOARD.SYS file not supported by the Microsoft version of the KEYB driver.)</ref>
<ref name="Patent_6973644">{{cite web |title=United States Patent 6,973,644 |url=http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=6973644.PN.&OS=PN/6973644&RS=PN/6973644 |access-date=2009-05-21  |archive-date=2017-03-05  |archive-url=https://web.archive.org/web/20170305001731/http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=6973644.PN.&OS=PN/6973644&RS=PN/6973644 |url-status=dead }}</ref>
<ref name="cran_r">{{Cite web|url=https://cran.r-project.org/doc/manuals/R-admin.html#Byte_002dcompiler|title=R Installation and Administration|website=cran.r-project.org}}</ref>
<ref name="SQLite">{{cite web |title=The SQLite Bytecode Engine |url=https://www.sqlite.org/opcode.html |access-date=29 August 2016 |archive-url=https://web.archive.org/web/20170414044139/http://sqlite.org/opcode.html |archive-date=14 April 2017 |url-status=dead }}</ref>
<ref name="Multiplan">{{cite book |title=Microsoft C Pcode Specifications |page=13 |quote=[[Multiplan]] wasn't compiled to [[machine code]], but to a kind of byte-code which was run by an [[interpreter (computing)|interpreter]], in order to make Multiplan portable across the widely varying hardware of the time. This byte-code distinguished between the machine-specific [[floating point format]] to calculate on, and an external (standard) format, which was [[binary-coded decimal|binary coded decimal]] (BCD). The PACK and UNPACK instructions converted between the two.}}</ref>
}}

[[Category:Virtualization]]
[[Category:Bytecodes|*]]