Add lock_globals() and unlock_globals() functions (for when you really need to use globals)

Tue, 31 Mar 2009 02:18:13 +0100

author
Matthew Wild <mwild1@gmail.com>
date
Tue, 31 Mar 2009 02:18:13 +0100
changeset 943
7f161205121d
parent 942
dae54304967d
child 944
2335ece4942d

Add lock_globals() and unlock_globals() functions (for when you really need to use globals)

prosody file | annotate | diff | comparison | revisions
--- a/prosody	Tue Mar 31 02:17:11 2009 +0100
+++ b/prosody	Tue Mar 31 02:18:13 2009 +0100
@@ -152,7 +152,17 @@
 end
 
 -- setup error handling
-setmetatable(_G, { __index = function (t, k) error("Attempt to read a non-existent global '"..k.."'", 2); end, __newindex = function (t, k, v) error("Attempt to set a global: "..tostring(k).." = "..tostring(v), 2); end });
+local locked_globals_mt = { __index = function (t, k) error("Attempt to read a non-existent global '"..k.."'", 2); end, __newindex = function (t, k, v) error("Attempt to set a global: "..tostring(k).." = "..tostring(v), 2); end }
+
+function unlock_globals()
+	setmetatable(_G, nil);
+end
+
+function lock_globals()
+	setmetatable(_G, locked_globals_mt);
+end
+
+lock_globals();
 
 eventmanager.fire_event("server-started");
 

mercurial