36. Appendix

36.1 Appendix A: Reserved Words

Keywords are defined in MaldaLang/Lexer.cs. fn and def are not reserved; the parser rejects them as function keywords. reply is a built-in function, not a reserved word.

if, else, while, for, foreach, function, return, var, const, print, input,
true, false, and, or, not, break, continue, try, catch, finally, throw,
match, case, default, defer,
class, new, this, super, extends, public, private, static, null, type, schema, api,
prompt, async, await,
actor, spawn, send, receive, self, on, then, timeout, message,
workflow, step, approval, wait, retry, backoff, delay, maxDelay, compensate, onReject,
component, property,
dict, graph, directed, undirected, in,
using, include, import, export

36.2 Appendix B: Operator Precedence

The table below mirrors the descent order of the reference parser (MaldaLang/Parser/Parser.cs), from highest precedence (binds tightest) to lowest.

36.3 Appendix C: Object-Oriented Concepts Summary

Classes

• Blueprint for creating objects
• Contains fields (data) and methods (behavior)
• Can have constructors for initialization

Objects

• Instances of classes created with new keyword
• Each object has its own copy of instance fields
• Share methods defined in the class

Inheritance

• Classes can extend other classes using extends
• Child classes inherit parent's public members
• Can override parent methods
• Use super to call parent constructor/methods

Encapsulation

• Access modifiers control visibility:
  • public: Accessible from anywhere
  • private: Accessible only within the class
• Fields should typically be private, accessed via public methods

Polymorphism

• Method overriding allows child classes to provide different implementations
• Objects of child type can be treated as parent type

Static Members

• Belong to the class, not instances
• Accessed via class name
• Shared across all instances

36.4 Appendix D: Command-line reference

Summary of malda CLI commands. See 32. Personal Assistant and CLI for details on the assistant, config, and cron.

36.5 Appendix E: Deploy and observability contract baseline

The malda deploy command in this baseline validates configuration contracts and exits without starting deployment orchestration.

Default input contracts:

• config/deploy.example.json
• config/environments/prod.json (or --profile dev|test|prod)
• config/observability.example.json

Minimum validated expectations:

• Health/readiness paths are present and wired consistently between deploy and environment profile contracts.
• Structured logging baseline uses JSON format and includes core fields (timestamp, level, message, environment/profile, optional correlation).
• Metrics endpoint wiring is present and consistent across profile and observability contracts.

36.6 Appendix F: Profiling MALDA programs

MALDA includes a built-in profiler for performance investigations. It can profile interpreted runs and transpiled executables and reports hotspots in terms of MALDA built-ins, functions, and statement locations.

Supported CLI flags:

• --profile - Enable profiling for the run or for the compiled executable.
• --profile-output <path> - Write the report to a file path.
• --profile-format text|json|both - Choose human-readable text, structured JSON, or both.
• --profile-periodic-seconds <N> - While running, rewrite the profile file(s) every N seconds of wall-clock time. Use 0 (default) for end-of-run only. Useful for long jobs so an interrupted run still leaves a recent partial report on disk.

JSON reports include a Partial field: true for periodic snapshots, false for the final write at exit. Periodic snapshots overwrite the same output path; they do not spam the console.

Examples:

malda my-script.malda --profile
malda my-script.malda --profile --profile-output profile.json --profile-format json
malda my-script.malda --profile --profile-output profile.json --profile-format json --profile-periodic-seconds 60
malda compile my-script.malda --mode transpile -o my-script.exe --profile --profile-output profile.json --profile-format json

The profiler currently reports:

• BuiltIns - aggregated built-in function timing
• Functions - aggregated MALDA function timing
• Statements - aggregated statement timing by MALDA source location

Each report entry includes call count, total time, average time, and self time. Expression-level profiling is intentionally not included in this first version to keep overhead practical.

36.7 Appendix G: Optional packs

Core MALDA keeps domain-specific packs out of the public core. The compiler still has string-only emit hooks for optional packs so separately distributed assemblies can plug in without becoming ProjectReferences of the core.

Vertical packs are not included in this open-source repository. If you maintain such a pack, load it with loadNativeModule(...) and ship the DLLs beside your app; core does not auto-register pack globals.