> I still think it's useful to have a mode where uncontrolled global > access is verboten and a compile-time error. The current workarounds > are not so elegant, often involving a custom build step that e.g. for > Lua 5.1 checks out any GETGLOBAL instructions. In both 5.1 and 5.2, the place to start patching is at singlevar in lparser.c, right after the call to singlevaraux. See for instance http://lua-users.org/lists/lua-l/2006-10/msg00206.html See also http://lua-users.org/lists/lua-l/2011-06/msg00091.html