* process exit change: close everything at GC when main state closes, not when atexit() handlers are processed

   * Lua 5.2-style module:
      * module() is no longer used to implement lanes.lua
      * a global "lanes" variable is no longer created when the module is required
      * the Lanes module table is returned instead
   * Lanes must be initialized before used:
      * the first occurence of 'require "lanes"' produces a minimal interface that only contains a configure() function
      * the remainder of the interface is made available once this function is called
      * subsequent calls to configure() do nothing
      * configure() controls the number of keeper states and the startup of timers
   * LuaJIT 2 compatibility
      * non-Lua functions are no longer copied by creating a C closure from a C pointer, but through 2-way lookup tables
      * this means that if a lane function body pulls non-Lua functions, the lane generator description must contain the list of libraries and modules that exports them
      * introduces a change in configuration .globals management: contents are copied *after* std libs are loaded
      * new .required configuration entry to list modules that must be require()'ed before lane body is transferred
   * lane:cancel() wakes up waiting lindas like what is done at lane shutdown

1 files changed, 3 insertions, 2 deletions

diff --git a/tests/irayo_closure.lua b/tests/irayo_closure.lua
index 3a82302..77ddbde 100644
--- a/tests/irayo_closure.lua
+++ b/tests/irayo_closure.lua
@@ -10,7 +10,8 @@ haven't investigated further.
 e.g. { globals = { data = 1, func = function() useclosurehere() end } }"
 ]]
 
-require "lanes"
+local lanes = require "lanes"
+lanes.configure( 1)
 
 local function testrun()
     assert( print )
@@ -20,7 +21,7 @@ local function testrun()
     return true
 end
 
--- When some function dereferences a global key, the asssociated global in the source state
+-- When some function dereferences a global key, the associated global in the source state
 -- isn't sent over the target lane
 -- therefore, the necessary functions must either be pulled as upvalues (hence locals)
 -- or the globals must exist in the target lanes because the modules have been required there