This issue list is now obsolete. Open issues have been moved to the github repo.
| 1 | Paths are not handled. The FSMLang executable must be executed in the directory containing the input file. The output will be placed in that same directory. | Open |
|---|---|---|
| 2 | Only one level of sub-machine is supported by the code genertors, while the parser handles many levels. This means that levels nested more than one level will not be generated, but no parsing error will be given. | Open |
| 3 | Sub-machines generate warning #188-D enumerated type mixed with another type when compiled with armcc. | Resolved |
| 4 | Cannot use both --core-logging-only and --generate-weak-fns. | Not reproduced. |
| 5 | sub-machines generate unnecessary state transition declarations. | Resolved |
| 6 | HSM switch machines generate enum mis-match compiler warnings with armcc | Resolved |
| 7 | sub-machine related declarations must precede fsm data struct declaration. | Resolved |
| 8 | When the transition keyword immediately follows the event and state lists, the parser thinks a sub-machine exists. | Resolved |
| 9 | C++ does not allow forward enum typedefs. | Resolved |
| 10 | RUN_STATE_MACHINE and DECLARE_xxx_MACHINE violate MISRA C:2012:20.7: Expressions resulting from the expansion of macro parameters shall be enclosed in parentheses. | Resolved |
| 11 | Newlines have crept back into the DBG_PRINTFs. | Resolved |
| 11 | Curly braces cannot appear in the native blocks. | Resolved |
| 12 | Macro initializing FSM struct malformed. | Resolved |
Please report any issues or concerns to FSMLang