deadproger / industrialc Goto Github PK

Problem:
Timeouts from ISR-driven processes are executed in background, not inside the ISR.
In this case, if timeout code is using any variables defined inside state body - we get a compiler error - these variables are local and don't even exist at the moment timeout code executes.

Example:
process some_proc : some_isr_hyperprocess {
state some_state {
int a; // in c code, a will be declared inside ISR body
...
timeout(a) { ... a =1; ... } // timeout condition and body will be outside ISR, in main loop
}
}

Possible solutions:
a) Prohibit use of local variables in timeouts. It would then be advisable to also change the syntax so that timeouts are defined outside state body (for clarity).
b) Detect this situation, make such variables global, simulate dynamic behavior by reinitializing them at the start of every state execution and protect with critical sections. (seems labor-intensive and not very transparent for the programmer)