Input mapping
I want an input mapping language. This idea has played at my mind for a while, but it's closer now than before to existing. My weird continuous language of months ago was an early attempt. Here are some thoughts.
It must not be Turing complete because every program must halt. It should be possible to graph the language: that is, it should be easy to describe the mapping in terms of the input mechanisms (what happens when I click this?) and in terms of the output mechanisms (how do I close this?). The extent to which this limits the language is evident, but it's very well worth it for the properties that are guaranteed.
Think of it as filling a finite set of cells on one tape with an admixture of cells from another tape.
It must not be Turing complete because every program must halt. It should be possible to graph the language: that is, it should be easy to describe the mapping in terms of the input mechanisms (what happens when I click this?) and in terms of the output mechanisms (how do I close this?). The extent to which this limits the language is evident, but it's very well worth it for the properties that are guaranteed.
Think of it as filling a finite set of cells on one tape with an admixture of cells from another tape.