From b335cbcc9f07dc71999b885ffa2962c0ec00f5eb Mon Sep 17 00:00:00 2001 From: Benoit Germain Date: Mon, 6 Jan 2014 10:40:14 +0100 Subject: fix on_state_create circular logic issue * if config.on_state_create() is a C function, call it by direct C closure reconstruction in newly created states * bumped version to 3.7.6 --- docs/index.html | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/index.html b/docs/index.html index f25463d..931a961 100644 --- a/docs/index.html +++ b/docs/index.html @@ -64,13 +64,13 @@


- Copyright © 2007-13 Asko Kauppi, Benoit Germain. All rights reserved. + Copyright © 2007-14 Asko Kauppi, Benoit Germain. All rights reserved.
Lua Lanes is published under the same MIT license as Lua 5.1 and 5.2.

- This document was revised on 20-Dec-13, and applies to version 3.7.5. + This document was revised on 06-Jan-14, and applies to version 3.7.6.

@@ -356,13 +356,17 @@ If provided, will be called in every created Lua state (keepers and lanes) right after initializing the base libraries. -
+
Typical usage is twofold: That way, all changes in the state can be properly taken into account when building the function lookup database. Default is nil. +
+ (Since version 3.7.6) If on_state_create() is a Lua function, it will be transfered normally before the call. +
+ If it is a C function, a C closure will be reconstructed in the created state from the C pointer. Lanes will raise an error if the function has upvalues. -- cgit v1.2.3-55-g6feb