no, initialize globals in symmetry with functions

Current plan: definitions can have arbitrary code. They'll be loaded
lazily when a specific name is invoked but has no binding. Implications:

- It'll be the responsibility of the code to define the name it's saved
  in. "Phony" names will result in some fragments of code repeatedly
  executing.

- Assigning a global to nil is a way to retrigger its initialization the
  next time it's needed.

I'm not sure how I feel about this sort of incompatibility with Lua. I
suppose we could avoid it by also tracking what definitions have already
been loaded in a run.

0 files changed, 0 insertions, 0 deletions