Skip to content

doActivity timing: start on entry and let completion wait for it #700

Open

Description

@fgmacedo

Why

invoke is how this library runs a doActivity, and it is the most used way to run work while in a state. UML starts the doActivity as part of entering the state and fires the completion only after it ends; the SCXML default starts invocations at the end of the macrostep and fires eventless transitions immediately.

Scope

  • A class-level flag for the start time of invocations (conflict K14 in the PSSM xfail map).
  • Completion of a state with a running doActivity waits for it (K2), built on the explicit completion spelling.
  • Defaults keep SCXML behavior.

Acceptance

PSSM cases coded conflict:K14 and conflict:K2 pass with the flag on both engines; W3C SCXML suite unchanged with defaults.

Depends on #699. Refs #692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementumlUML state machine semantics, tracked in #692

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions