2DGYDDD2XTGYTO3I6GGBFVAEOHYUNQE5G4QOPOSDM3O3JFSG76DQC
7I6ORCM4Q7FHMHFKWECNGO2H3VKEUSPS7K2L2JGGBXJB4X3DLSJAC
VCF6NJ5REA6CBIHJDKP4DVGKHG5CILQ77IHGYE2QPB4ANFHE5TKAC
IDGP4BJZTKAD6ZO4RLAWYVN6IFCMIM76G6HJGPTE27K4D6CDBUHQC
IXHSSD6U2EAJA5TJWC3UQ45XQHZVUWRU3GOIF43XJ6YPSWNPDO5QC
FS2ITYYHBLFT66YUC3ENPFYI2HOYHOVEPQIN7NQR6KF5MEK4NKZAC
25V2GA6JNWMYNBNFLBHFPJ5ZFYQ4E25E4XMTJSTQJGPPK56RSBAAC
* This approach puts one top-level definition per file, and so obscures the
order in which definitions are loaded. In particular, initializing a global
table to contain other global definitions will fail if you originally
authored the other global definitions after the table.
I never initialize global tables with other definitions. That kind of thing
happens in `on.initialize` (akin to `love.load`; see reference.md) or
`on.code_change`.
* Don't start the driver app while multiple freewheeling apps are running. If
you have a driver app running with one app, shut it down before you switch
apps.