rfc:ast_based_parsing_compilation_process
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
rfc:ast_based_parsing_compilation_process [2013/08/24 19:13] – add ML discussion nikic | rfc:ast_based_parsing_compilation_process [2014/08/18 16:46] – nikic | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Request for Comments: Moving to an AST-based parsing/ | + | ====== Request for Comments: Moving to an AST-based parsing/ |
* Date: 2012-09-04 | * Date: 2012-09-04 | ||
* Author: Nikita Popov < | * Author: Nikita Popov < | ||
- | * Status: | + | * Status: |
* [[http:// | * [[http:// | ||
+ | * Superseded by: [[rfc: | ||
===== Introduction ===== | ===== Introduction ===== | ||
+ | |||
+ | **Note: This RFC has been superseded by another [[rfc: | ||
Currently PHP uses a single-pass compilation process, i.e. the parser directly invokes opcode compilation routines. Most other languages on the other hand use an intermediary structure to separate those two phases: The parser only emits an abstract syntax tree (AST), which is then used by a separate compiler to emit instructions. The use of an AST decouples the two phases and as such allows for greater flexibility and deeper analysis. | Currently PHP uses a single-pass compilation process, i.e. the parser directly invokes opcode compilation routines. Most other languages on the other hand use an intermediary structure to separate those two phases: The parser only emits an abstract syntax tree (AST), which is then used by a separate compiler to emit instructions. The use of an AST decouples the two phases and as such allows for greater flexibility and deeper analysis. |
rfc/ast_based_parsing_compilation_process.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1