New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transitions hint other transitions. #6

vanrein opened this Issue Jan 28, 2018 · 1 comment


None yet
1 participant

vanrein commented Jan 28, 2018

This is an auto-trigger capability, and may be centered around numbered hints that end up in flags carried around the loop; the loop can (if hints exist, and Colour changed since the last attempt) fold over the transmap to process those that are hinted, and to collect new hints. (One bit can hint that something was done at all.)

Application-driven hints can be returned as {retry,Hint(s)} and processed upon later process_hints() invocation, or automatically retried for asynchronous signals (without EventData).

The big thing about hints is how they shall be configured; it requires application logic; this is not available to the compiler, but it is during indstantiation.

Note that hints in no way undermine Petri Net semantics, where transitions may fire at random. The hint behaviour can be manually crafted by sending signals from transition callbacks to the application logic.

@vanrein vanrein created this issue from a note in Erlang target code (Deferred beyond 1.0) Jan 28, 2018


This comment has been minimized.


vanrein commented Feb 11, 2018

One thing that appears to be useful, as we find during the KXOVER field test, is to provide the application logic for a transition with transitions to trigger on success and failure. This might be specified in a separate simple CSV table (and produced in a spreadsheet or editor).

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