I just realized that the PADMAP.TXT support in this was
completely untested
broken due to copy-paste mistake from NeoYume (which handles input drivers in a silly way)
the on-screen status report ("%d rules") was always zero regardless because I used an outdated(?) version of padmap_parser that didn't count the rules ( @ersmith shouldn't flexspin warn when you call a Spin2 function with no returns in an assignment like tmp := padmap.parse(...)?)
I profusely apologize for such buffoonery and a fix has been deployed to all relevant branches
The failure to warn about tmp := padmap.parse(...) is left over from Spin1, where functions always implicitly return a value. You're right, in Spin2 we should warn about this.
Comments
I just realized that the PADMAP.TXT support in this was
tmp := padmap.parse(...)?)I profusely apologize for such buffoonery and a fix has been deployed to all relevant branches
The failure to warn about
tmp := padmap.parse(...)is left over from Spin1, where functions always implicitly return a value. You're right, in Spin2 we should warn about this.