From fffa17d7e28f4a3147adf1f2ae2a73c4b0f7b945 Mon Sep 17 00:00:00 2001 From: Benoit Germain Date: Wed, 12 Jun 2024 11:26:38 +0200 Subject: Add support for to-be-closed linda --- docs/index.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/index.html b/docs/index.html index 10bf832..be8324c 100644 --- a/docs/index.html +++ b/docs/index.html @@ -70,7 +70,7 @@

- This document was revised on 15-May-24, and applies to version 4.0.0. + This document was revised on 12-Jun-24, and applies to version 4.0.0.

@@ -1196,13 +1196,16 @@ 

-	h = lanes.linda([opt_name, [opt_group]])
+	h = lanes.linda([name],[group],[close_handler])

+ Arguments to lanes.linda() can be provided in any order, as long as there is a single string, a single number, and a single callable value (all are optional).
Converting the Linda to a string will yield the provided name prefixed by "Linda: ".
If opt_name is omitted, it will evaluate to an hexadecimal number uniquely representing that Linda when the Linda is converted to a string. The value is the same as returned by linda:deep().
- If opt_name is "auto", Lanes will try to construct a name from the source location that called lanes.linda(). If that fails, the Linda name will be "<unresolved>". + If opt_name is "auto", Lanes will try to construct a name from the source location that called lanes.linda(). If that fails, the Linda name will be "<unresolved>".
+ If Lanes is configured with more than one Keeper state, group is mandatory.
+ If the Linda is to-be-closed (Lua 5.4+), and a close_handler is provided, it will be called with all the provided arguments. For older Lua versions, its presence will cause an error. 

-- 
cgit v1.2.3-55-g6feb