Skip to content
EN FR

FPL Developer — Anti-Patterns

Documentation status: guide — see Maturity and evidence.

  • Encoding business state in hidden evaluator globals.
  • Depending on undocumented evaluation-state numbers or private evaluator classes.
  • Introducing side effects into expressions that appear pure.
  • Writing documentation examples that are not checked against the current grammar.
  • Treating a design proposal as an implemented language construct.
  • Reimplementing host-language control flow when a stable FPL construct already expresses the intent.
  • Coupling an expression to one transport, UI or storage backend.