From 8fb8dc1edeceae9fff65463cd80da05d8995fb7f Mon Sep 17 00:00:00 2001 From: Benoit Germain Date: Wed, 13 Mar 2013 20:48:01 +0100 Subject: version 3.5.2 * stricter validation of with_timers config option: validator was accepting any non-boolean value * new configuration option protect_allocator for VMs with thread unsafe allocators (such as LuaJIT) * removed some obsolete bits of dead code --- docs/index.html | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/index.html b/docs/index.html index 89710ab..98c1d3d 100644 --- a/docs/index.html +++ b/docs/index.html @@ -70,7 +70,7 @@

- This document was revised on 12-Feb-13, and applies to version 3.5.1. + This document was revised on 13-Mar-13, and applies to version 3.5.2.

@@ -284,11 +284,24 @@ .with_timers - nil/false/anything + nil/false/true + + + If equal to false or nil, Lanes doesn't start the timer service, and the associated API will be absent from the interface (see below). + Default is true. + + + + + + .protect_allocator + + + nil/false/true - If equal to false, Lanes doesn't start the timer service, and the associated API will be absent from the interface (see below). - Any other non-nil value starts the timer service. Default is true. + (Since v3.5.2) If equal to true, Lanes wraps all calls to the state's allocator function inside a mutex. Useful when running Lanes with LuaJIT, whose allocator is not threadsafe. + Default is nil. -- cgit v1.2.3-55-g6feb