Byte code

Examples

• ActionScript executes in the ActionScript Virtual Machine (AVM), which is part of Flash Player and AIR. ActionScript code is typically transformed into bytecode format by a compiler. Examples of compilers include one built into Adobe Flash Professional and one built into Adobe Flash Builder and available in the Adobe Flex SDK.
• Adobe Flash objects
• BANCStar, originally bytecode for an interface-building tool but used also as a language. BANCStar was designed as an internal machine language generated by a "screen generator" tool for financial applications, but was later written directly by programmers as a de facto language in its own right.
• Berkeley Packet Filter
• EBPF
• Berkeley Pascal
• Byte Code Engineering Library
• C to Java virtual machine compilers
• CLISP implementation of Common Lisp used to compile only to bytecode for many years; however, now it also supports compiling to native code with the help of GNU lightning
• CMUCL and Scieneer Common Lisp implementations of Common Lisp can compile either to native code or to bytecode, which is far more compact
• Common Intermediate Language executed by Common Language Runtime, used by .NET languages such as C#
• Dalvik bytecode, designed for the Android platform, is executed by the Dalvik virtual machine
• Dis bytecode, designed for the Inferno (operating system), is executed by the Dis virtual machine
• EiffelStudio for the Eiffel programming language
• EM, the Amsterdam Compiler Kit virtual machine used as an intermediate compiling language and as a modern bytecode language
• Emacs is a text editor with most of its functions implemented by Emacs Lisp, its built-in dialect of Lisp. These features are compiled into bytecode. This architecture allows users to customize the editor with a high level language, which after compiling into bytecode yields reasonable performance.
• Embeddable Common Lisp implementation of Common Lisp can compile to bytecode or C code
• Common Lisp provides a disassemble function which prints to the standard output the underlying code of a specified function. The result is implementation-dependent and may or may not resolve to bytecode. Its inspection can be utilized for debugging and optimization purposes. Steel Bank Common Lisp, for instance, produces: