Okay, okay, I give -- hierarchic namespaces are the way to go. Makes
local overrides somewhat interesting, but we'll burn that bridge when
we get to it.

That does, though, argue that we need to revisit the global access
opcodes. If we're going hierarchic, and we want to separate out the
name from the namespace, that would seem to argue that we'd want it
to look  like:

   find_global P1, ['global', 'namespace', 'hierarchy'], "thingname"

That is, split the namespace path from the name of the thing, and
make the namespace path a multidimensional key.

Or I suppose we could just punt and toss the special global access
entirely and make the global namespace a hash 'o hashes hanging off
the interpreter and access it like any other variable, but that makes
local obscuration of the namespace somewhat difficult and I'd rather
not for right now.

This'd be the time to weigh in on it, folks...
--
                                         Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
d...@sidhe.org                         have teddy bears and even
                                       teddy bears get drunk