summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenoit Germain <bnt.germain@gmail.com>2018-11-28 17:00:45 +0100
committerBenoit Germain <bnt.germain@gmail.com>2018-11-28 17:00:45 +0100
commit123418beab3404848b27471e2ecfe5d1215c1fcc (patch)
tree2b694f56b93535f2ac775a7b9cc887bf7986e117
parent135883062fe4eacb1a49dc90a535ae0d39349236 (diff)
downloadlanes-123418beab3404848b27471e2ecfe5d1215c1fcc.tar.gz
lanes-123418beab3404848b27471e2ecfe5d1215c1fcc.tar.bz2
lanes-123418beab3404848b27471e2ecfe5d1215c1fcc.zip
Split a megafunction in smaller parts
-rw-r--r--index.html3
1 files changed, 2 insertions, 1 deletions
diff --git a/index.html b/index.html
index 460a786..db8e7a0 100644
--- a/index.html
+++ b/index.html
@@ -1553,7 +1553,7 @@ events to a common Linda, but... :).</font>
1553 1553
1554<h3 id="clonable_userdata">Clonable full userdata in your own apps</h3> 1554<h3 id="clonable_userdata">Clonable full userdata in your own apps</h3>
1555<p> 1555<p>
1556 Starting with version 3.13, a new way of passing full userdata across lanes uses a new <tt>__lanesclone</tt> metamethod. A typical implementation would look like: 1556 Starting with version 3.13.0, a new way of passing full userdata across lanes uses a new <tt>__lanesclone</tt> metamethod. A typical implementation would look like:
1557<table border="1" bgcolor="#FFFFE0" cellpadding="10" style="width:50%"><tr><td><pre> 1557<table border="1" bgcolor="#FFFFE0" cellpadding="10" style="width:50%"><tr><td><pre>
1558static int clonable_lanesclone( lua_State* L) 1558static int clonable_lanesclone( lua_State* L)
1559{ 1559{
@@ -1580,6 +1580,7 @@ static int clonable_lanesclone( lua_State* L)
1580</p> 1580</p>
1581 1581
1582<p> 1582<p>
1583 <b>NOTE</b>: In the event the source userdata has uservalues, it is not necessary to create them for the clone, Lanes will handle their cloning.<br/>
1583 Of course, more complex objects may require smarter cloning behavior than a simple <tt>memcpy</tt>. Also, the module initialisation code should make each metatable accessible from the module table itself as in: 1584 Of course, more complex objects may require smarter cloning behavior than a simple <tt>memcpy</tt>. Also, the module initialisation code should make each metatable accessible from the module table itself as in:
1584<table border="1" bgcolor="#FFFFE0" cellpadding="10" style="width:50%"><tr><td><pre> 1585<table border="1" bgcolor="#FFFFE0" cellpadding="10" style="width:50%"><tr><td><pre>
1585int luaopen_deep_test(lua_State* L) 1586int luaopen_deep_test(lua_State* L)