Lane userdata implementation refactoring:

    - Refactor lane proxy implementation: it is now a full userdata instead
      of a table, and its methods are implemented in C instead of Lua.
      * its metatable is no longer accessible.
      * writing to the proxy raises an error.
      * it is no longer possible to overwrite its join() and cancel() methods
    - when a deep userdata idfunc requests a module to be required, manually
      check that it is not loaded before requiring it instead of relying on
      the require function's loop detection feature.
    - when a module must be required, raise an error if the 'require' function
      is not found in the target state.
    - we know Lanes is loaded in the master state, so we don't force it
      to be required in every lane too when a linda deep userdata is copied.

1 files changed, 27 insertions, 0 deletions

diff --git a/tests/protectproxy.lua b/tests/protectproxy.lua
new file mode 100644
index 0000000..57ca831
--- /dev/null
+++ b/tests/protectproxy.lua
@@ -0,0 +1,27 @@
+require "lanes"
+
+local body = function( param)
+        print ( "lane body: " .. param)
+        return 1
+end
+
+local gen = lanes.gen( "*", body)
+
+local mylane = gen( "hello")
+
+local result = mylane[1]
+
+-- make sure we have properly protected the lane
+
+-- can't access the metatable
+print( "metatable:" .. tostring( getmetatable( mylane)))
+
+-- can't write to the userdata
+print( "lane result: " .. mylane[1])
+
+-- read nonexistent values -> nil
+print "reading nonexistent return value"
+a = mylane[2]
+
+print "writing to the lane -> error"
+mylane[4] = true