FPLN Evaluation Modes
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
FPLN evaluation modes must be understood within the concrete execution model rather than assuming a single universal mode.
Execution contexts carry the state and environment in which runtime instructions, actions and processes operate. The source separates metadata and logical definitions from interpreter stacks, instruction trees and operational state. A call must be interpreted in the correct context, including ownership and lifetime.
Engineering rules
- Select the relevant execution engine for the declared operation.
- Make input context, output, error and cancellation behavior observable.
- Keep reusable definitions separate from mutable operation and session state.
- Release contexts, cursors and resources at their intended lifetime boundary.
Chapter outline (original LaTeX headings)
- Purpose of This Chapter
- Where FPLN Fits in the Runtime
- From Script Text to Runtime Evaluation
- The Context as Execution Boundary
- Execution Modes
- The Process Execution Engine
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/fpln-execution-model.tex.