Compiler terms
How source code becomes something a machine can actually run
Compilers are the translators that turn human-readable source code into something a machine can execute. This category covers lexing, parsing, abstract syntax trees, semantic analysis, optimisation passes, code generation, and just-in-time compilation. Understanding how compilers work illuminates why languages behave the way they do and how to write code that compiles to faster output.
Dead Code Elimination PHP 7.4+
A compiler and static analysis optimisation that identifies and removes code that can never be executed or whose result is never used.
1mo ago
compiler intermediate
Type Inference PHP 7.0+
The compiler's ability to automatically deduce the type of an expression without an explicit annotation, based on context and assigned values.
1mo ago
compiler intermediate
Ahead-of-Time vs Just-in-Time Compilation
AOT compiles all code before execution (C, Go, Rust — fast startup, predictable performance). JIT compiles hot paths at runtime (PHP 8+, JVM — adapts to actual usage patterns).
2mo ago
compiler intermediate
Bytecode VMs PHP 5.0+
Zend Engine (PHP), JVM (Java/Kotlin), CLR (.NET) — all compile source to platform-independent bytecode then interpret or JIT-compile to native code.
2mo ago
compiler intermediate
Memory Management — Stack vs Heap PHP 5.0+
The stack holds function call frames with fixed-size local variables — fast, automatic, limited. The heap holds dynamically allocated objects — flexible, managed by GC, slower.
2mo ago
compiler intermediate
Transpilation Converting source code from one language or version to another at the same abstraction level — Babel transpiles modern JS to older JS, Rector transpiles old PHP to new PHP.
2mo ago
compiler intermediate