2 crash fixes and 1 experiment

* bumped version to 3.8.3
* fixed a possible Lua stack overflow when sending complex function
through lindas or as lane body
* experimental: lanes.nameof() scans the registry if a regular search
didn't yield anything interesting
* fixed lanes.nameof() misbehaving when encountering a LUA_TTHREAD
object

1 files changed, 7 insertions, 3 deletions

diff --git a/docs/index.html b/docs/index.html
index c662a14..f639f18 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -70,7 +70,7 @@
                         </p>
 
                         <p>
-                                This document was revised on 22-Jan-14, and applies to version <tt>3.8.2</tt>.
+                                This document was revised on 22-Jan-14, and applies to version <tt>3.8.3</tt>.
                         </p>
                 </font>
         </center>
@@ -645,8 +645,8 @@
 </p>
 
 <p>
-    If a lane body pulls a C function imported by a module required before Lanes itself (thus not through a hooked <tt>require</tt>), the lane generator creation will raise an error.
-    The function name it shows is a path where it was found by scanning <tt>_G</tt>. As a utility, the name guessing functionality is exposed as such:
+        If a lane body pulls a C function imported by a module required before Lanes itself (thus not through a hooked <tt>require</tt>), the lane generator creation will raise an error.
+        The function name it shows is a path where it was found by scanning <tt>_G</tt>. As a utility, the name guessing functionality is exposed as such:
 
         <table border="1" bgcolor="#E0E0FF" cellpadding="10" style="width:50%">
                 <tr>
@@ -657,6 +657,10 @@
         </table>
 </p>
 
+<p>
+        Starting with version 3.8.3, <tt>lanes.nameof()</tt> searches the registry as well.
+</p>
+
 <h3>Free running lanes</h3>
 
 <p>