Micro-toolkit

microfsm

Ad-hoc switch statements make state transitions hard to inspect.

A table-driven finite-state-machine engine keeps states, events and actions explicit.

DevelopmentMITC99
Last verified
Not audited against current README/docs
Platform scope
Portable C99; integration depends on caller-provided adapters

What it solves

Ad-hoc switch statements make state transitions hard to inspect.

How it works

1Event2transition table3action4next state

Use it when

Model a device operating mode
Centralize guarded transitions
Test transitions without hardware

Quick Start

#include "mfsm.h"
/* Define the documented transition table, initialize, then dispatch an event. */

Engineering evidence

  • Toolkit integration matrix maps the public header mfsm.h

Known limits

  • Application owns concurrency and side effects