* Move to new ring buffers or slurp entire source
* Add 'include' feature
* Add ability to define functions

That way, the configuration file can include a common file containing
functions that hide common idiom from each behaviour file, and a
backend-dependent file that can be used to abstract the database
somewhat from the behaviour file.

Semantics: A/V pair lists stay global, it's simply a gosub a la basic.