Editing Compiler (section)

==Comparison with interpreter==

With respect to making source code runnable, an [[interpreter (computing)|interpreter]] provides a similar function as a compiler, but via a different mechanism. An interpreter executes code without converting it to machine code.<ref name="dragon"/>{{rp|p2}} Some interpreters execute source code while others execute an intermediate form such as [[bytecode]].

A program compiled to native code tends to run faster than if interpreted. Environments with a bytecode intermediate form tend toward intermediate speed. [[Just-in-time compilation]] allows for native execution speed with a one-time startup processing time cost.

[[Low-level programming language]]s, such as [[assembly language|assembly]] and [[C (programming language)|C]], are typically compiled, especially when speed is a significant concern, rather than [[cross-platform]] support. For such languages, there are more one-to-one correspondences between the source code and the resulting [[machine code]], making it easier for programmers to control the use of hardware.

In theory, a programming language can be used via either a compiler or an interpreter, but in practice, each language tends to be used with only one or the other. None-the-less, it is possible to write a compiler for a languages that is commonly interpreted. For example, [[Common Lisp]] can be compiled to Java bytecode (then interpreted by the [[Java virtual machine]]), C code (then compiled to native machine code), or directly to native code.