ochre-lang

Copperbox revision 3166.

More work on supporting tuples, binding multiple return opcodes (e.g. ins, pan) is now possible.

However, my thinking has moved on since yesterday - I now think tuples should be first class, whereas yesterday I thought they would only be needed for destructuring at opcode binding sites (ins, pan again). If tuples aren't first class we can't write methods that return tuples, this is a too severe restriction as it limits modularity.

Because Csound doesn't have tuples, I will need to think carefully about how to implement them - they must be eliminated in translation.