See also http://lua-users.org/lists/lua-l/2006-10/msg00206.html
That is quite interesting. But this solution (if I understand it correctly)
depends on a Lua function declared somewhere else. So Lua files now depend
on each other at parse time. Currently you can parse each Lua file by
itself.
That code was just a prof-of-concept to show a general solution. You
can simplify it a lot by freezing a specific policy into the parser,
as I did earlier in this thread, raising an error for untagged
globals. You'd have a modified Lua interpreter but it would be uniform
for all your scripts.
I will consider it if I ever embedd another version of Lua (I am
currently at 5.2). The thing is, I try to stay as close to vanilla
Lua as possible.
So I am almost as conservative in adding extra features as the Lua
team is ;-)
--
Thomas
