Multiverse compatibility

* bumped version to 3.9.2
* Internal rework: the whole Lanes engine now works "per universe" to
allow concurrent Lanes execution in more than one embedded master state
* this universe is a full userdata created in the master state,
selfdestruct_gc is the __gc for this userdata
* most of what was initialized only once is now per-universe
* Fixed potential crashes at desinit if problems occur during keeper
states initialisation
* Fixed require() not always serialized properly
* Raise an error instead of crashing on deep userdata prelude memory
allocation failure
* Added forgotten mutex desinitialisation at universe shutdown

2 files changed, 15 insertions, 11 deletions

diff --git a/comparison.html b/comparison.html
index bebc68b..8e28f55 100644
--- a/comparison.html
+++ b/comparison.html
@@ -32,7 +32,7 @@ With the introduction of Lindas (Jun-2008), Lua Lanes simplifies its API while
 simultaneously adding more power and speed.
 
 Pros:
-    - regular Lua 5.1 module
+    - regular Lua 5.1/5.2 module
     - completely separate Lua states, one per OS thread
     - message passing, or shared data using Lindas
     - no application level locking, ever
@@ -54,7 +54,7 @@ Cons:
 
 Sample:
 <<
-  require "lanes"
+  lanes = require "lanes".configure()
   
   local function calculate(a,b,c)
     if not a then 
@@ -63,9 +63,9 @@ Sample:
     return a+b+c
   end
 
-  local h1= lanes.new(calculate)(1,2,3)
-  local h2= lanes.new(calculate)(10,20,30)
-  local h3= lanes.new(calculate)(100,200,300)
+  local h1= lanes.gen("base", calculate)(1,2,3)
+  local h2= lanes.new("base", calculate)(10,20,30)
+  local h3= lanes.new("base", calculate)(100,200,300)
 
   print( h1[1], h2[1], h3[1] )     -- pends for the results, or propagates error
 <<
@@ -304,11 +304,13 @@ Cons:
 <!-- footnotes +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
 <hr/>
 
-<p>For feedback, questions and suggestions:
-<UL>
-    <li><A HREF="http://luaforge.net/projects/lanes">Lanes @ LuaForge</A></li>
-    <li><A HREF="mailto:akauppi@gmail.com">the author</A></li>
-</UL>
+<p>
+        For feedback, questions and suggestions:
+        <ul>
+                <li><A HREF="http://github.com/LuaLanes/lanes">Lanes @ GitHub</A></li>
+                <li><A HREF="mailto:bnt.germain@gmail.com">the maintainer</A></li>
+                <li><A HREF="http://www.lua.org/lua-l.html">the lua mailing list</A></li>
+        </ul>
 </p>
 
 <!--
diff --git a/index.html b/index.html
index c6d612f..6337647 100644
--- a/index.html
+++ b/index.html
@@ -70,7 +70,7 @@
                         </p>
 
                         <p>
-                                This document was revised on 17-Feb-14, and applies to version <tt>3.9.1</tt>.
+                                This document was revised on 26-Feb-14, and applies to version <tt>3.9.2</tt>.
                         </p>
                 </font>
         </center>
@@ -105,6 +105,7 @@
                 <li>Threads can be given priorities.</li>
                 <li>Lanes are cancellable, with proper cleanup.</li>
                 <li>No Lua-side application level locking - ever!</li>
+                <li>Several totally independant Lanes universes may coexist in an application, one per "master" Lua state.</li>
         </ul>
 
 
@@ -114,6 +115,7 @@
                 <li>Coroutines are not passed between states.</li>
                 <li>Sharing full userdata between states needs special C side preparations (-&gt; <A HREF="#deep_userdata">deep userdata</A>).</li>
                 <li>Network level parallelism not included.</li>
+                <li>Just like independant Lua states, Lanes universes cannot communicate together.</li>
         </ul>
 </p>