Re: Say No to global-by-default (summary of the discussion)

[Luiz Henrique de Figueiredo <lhf@...>]

> 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.