bytecode compiler

The bytecode compiler and most core classes are written in pure Ruby.

Version 1.2 includes an interface, bytecode compiler, run-time system and documentation.

Bytecode compilers for Java, Python, and many more are also a subtype of this.

Several C to bytecode compilers exist:

Compilers from bytecode to machine code are easier to write, because the portable bytecode compiler has already done much of the work.

Bytecode compiler and interpreter (shrouder)

RapidQ features a bytecode compiler that produces stand alone executables by binding the generated bytecode with the interpreter.

Pnuts has since been extended, mainly focusing on essential functionality required for a Java-based scripting engine, such as a module system and bytecode compiler.

OCaml's toolset includes an interactive top level interpreter, a bytecode compiler, and an optimizing native code compiler.

There are, however, bytecode compilers available for other languages such as Ada, JavaScript, Python, and Ruby.

Racket's compiler is a bytecode compiler that translates to an internal bytecode format that is run by the Racket virtual machine.

The virtual machine also contained bytecode compilers for the x86 and PowerPC architectures, executing QVM instructions via an interpreter.

The target platform of Java's bytecode compiler is the Java platform, and the bytecode is either interpreted or compiled into machine code by the JVM.

The York Haskell Compiler (or Yhc) is an open source bytecode compiler for the functional programming language Haskell; it primarily targets the Haskell '98 standard.

Not Quite C (NQC) is a programming language, application programming interface (API), and native bytecode compiler toolkit for the Lego Mindstorms, Cybermaster and LEGO Spybotics systems.

CLISP includes an interpreter, a bytecode compiler, debugger, socket interface, high-level foreign language interface, strong internationalization support, and two object systems: Common Lisp Object System (CLOS) and metaobject protocol (MOP).

That requires C to bytecode compilers to provide their own lax machine abstraction, for instance producing compiled code that uses a Java array to represent main memory (so pointers can be compiled to integers), and linking the C library to a centralized Java class that emulates system calls.