From be2f2b4314799d38901c9e80dd35dee63f541c90 Mon Sep 17 00:00:00 2001 From: Benoit Germain Date: Tue, 26 Mar 2024 11:36:30 +0100 Subject: C++ migration: refactor AllocatorDefinition and ProtectedAllocator into classes --- docs/index.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs') 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 @@
-
	struct { lua_Alloc allocF; void* allocUD;}
+
	struct { lua_Alloc allocF; void* allocUD; }
- The contents will be used to create the state with lua_newstate( allocF, allocUD). + The contents will be used to create the state with lua_newstate(allocF, allocUD). 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. - Note however that linda deep proxy are allocated with the allocator from the master state, because they are not tied to a particular state. @@ -364,7 +363,7 @@ (Since v3.16.1)
- Controls which allocator is used for Lanest internal allocations (for keeper and deep userdata management). + Controls which allocator is used for Lanes internal allocations (for keeper, linda and lane management). If "libc", Lanes uses realloc and free.
If "allocator", Lanes uses whatever was obtained from the "allocator" setting.
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). -- cgit v1.2.3-55-g6feb