aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/index.html7
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/index.html b/docs/index.html
index e9c3239..b48c527 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -345,13 +345,12 @@
345 <table border="1" bgcolor="#E0E0FF" cellpadding="10" style="width:50%"> 345 <table border="1" bgcolor="#E0E0FF" cellpadding="10" style="width:50%">
346 <tr> 346 <tr>
347 <td> 347 <td>
348 <pre> struct { lua_Alloc allocF; void* allocUD;}</pre> 348 <pre> struct { lua_Alloc allocF; void* allocUD; }</pre>
349 </td> 349 </td>
350 </tr> 350 </tr>
351 </table> 351 </table>
352 The contents will be used to create the state with <tt>lua_newstate( allocF, allocUD)</tt>. 352 The contents will be used to create the state with <tt>lua_newstate(allocF, allocUD)</tt>.
353 This option is mostly useful for embedders that want to provide different allocators to each lane, for example to have each one work in a different memory pool thus preventing the need for the allocator itself to be threadsafe. 353 This option is mostly useful for embedders that want to provide different allocators to each lane, for example to have each one work in a different memory pool thus preventing the need for the allocator itself to be threadsafe.
354 Note however that linda deep proxy are allocated with the allocator from the master state, because they are not tied to a particular state.
355 </td> 354 </td>
356 </tr> 355 </tr>
357 356
@@ -364,7 +363,7 @@
364 </td> 363 </td>
365 <td> 364 <td>
366 (Since v3.16.1)<br /> 365 (Since v3.16.1)<br />
367 Controls which allocator is used for Lanest internal allocations (for keeper and deep userdata management). 366 Controls which allocator is used for Lanes internal allocations (for keeper, linda and lane management).
368 If <tt>"libc"</tt>, Lanes uses <tt>realloc</tt> and <tt>free</tt>.<br /> 367 If <tt>"libc"</tt>, Lanes uses <tt>realloc</tt> and <tt>free</tt>.<br />
369 If <tt>"allocator"</tt>, Lanes uses whatever was obtained from the <tt>"allocator"</tt> setting.<br /> 368 If <tt>"allocator"</tt>, Lanes uses whatever was obtained from the <tt>"allocator"</tt> setting.<br />
370 This option is mostly useful for embedders that want control all memory allocations, but have issues when Lanes tries to use the Lua State allocator for internal purposes (especially with LuaJIT). 369 This option is mostly useful for embedders that want control all memory allocations, but have issues when Lanes tries to use the Lua State allocator for internal purposes (especially with LuaJIT).