"Ray Dillinger" <bear@sonic.net> wrote in message
< ...> In most languages, scope rules require the variable name, the function> name, and a unique identifier for the activation frame. In C and C++,> however (and a few other languages) you also need the code address of> the reference, because the baroque scoping rules include variables whose> scope is a smaller unit than a full function.>> Hope that helps.

Yes it does, especially the last paragraph. It seems that scope is a very
very key concept of a language. If I was building a toolkit to implement
languages with (I wish there was such a thing, btw), there would be data
structures/mechanisms/algorithms to make scope "a first class citizen", so
to speak. From one of the other replies, a potential starting point for the
aforementioned could be having separate symbol tables per each scope. Or at
least hierarchial ones per "major" (translation unit?) scope.