The Evolution of Lua¶
Ierusalimschy, R., de Figueiredo, L. H., & Celes, W. (2007). The Evolution of Lua. Proceedings of the Third ACM SIGPLAN History of Programming Languages Conference (HOPL III), 2-1.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Inner-Platform Effect
- A second compression is a shared intervention catalogue: recognise the inner platform before it accretes (architecture review flags incremental extensions that look like host facilities); provide escape hatches (the sub-system routes uncommon cases to the host via a small embedded scripting language or callback); bound the customisation surface (deliberate non-extensibility of certain features, with documented reasons); re-architect when recognised (replace EAV with typed tables, YAML-with-conditionals with a real language, cron-plus-shell with a scheduler); and use the host's facilities directly (embedded Lua, JavaScript, or WASM rather than a custom expression language; SQL in templates rather than a template-engine query DSL).
This sourceDocuments Lua's design as a lightweight embeddable scripting language used as the host-language escape hatch in engines, databases, and editors rather than building a custom expression language.
Supported in partVerified against the work's full text
The Lua history supports embedding a small scripting language in a host instead of extending a custom configuration language, one item of the five-part intervention catalogue.
“Lua is designed to be embedded into a host application so that users can control how the application”
- A second compression is a shared intervention catalogue: recognise the inner platform before it accretes (architecture review flags incremental extensions that look like host facilities); provide escape hatches (the sub-system routes uncommon cases to the host via a small embedded scripting language or callback); bound the customisation surface (deliberate non-extensibility of certain features, with documented reasons); re-architect when recognised (replace EAV with typed tables, YAML-with-conditionals with a real language, cron-plus-shell with a scheduler); and use the host's facilities directly (embedded Lua, JavaScript, or WASM rather than a custom expression language; SQL in templates rather than a template-engine query DSL).
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:395390db1bef · see in the full table