lua/lstate.c, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12026-04-23T21:00:23+00:00new macro 'setnilvalue2s'2026-04-23T21:00:23+00:00Roberto Iroberto@inf.puc-rio.br2026-04-23T21:00:23+00:00urn:sha1:ae23e726018bd31a25c1279600328d90207ec81cMore effort in avoiding errors in finalizers2026-01-11T18:36:03+00:00Roberto Iroberto@inf.puc-rio.br2026-01-11T18:36:03+00:00urn:sha1:2a7cf4f319fc276f4554a8f6364e6b1ba4eb2ded
Before calling a finalizer, Lua not only checks stack limits, but
actually ensures that a minimum number of slots are already allocated
for the call. (If it cannot ensure that, it postpones the finalizer.)
That avoids finalizers not running due to memory errors that the
programmer cannot control.
A coroutine can close itself2025-06-12T14:15:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-12T14:15:09+00:00urn:sha1:fd897027f19288ce2cb0249cb8c1818e2f3f1c4c
A call to close itself will close all its to-be-closed variables and
return to the resume that (re)started the coroutine.
New function 'resetCI'2025-03-17T17:32:08+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-03-17T17:32:08+00:00urn:sha1:921832be8d7f687d2cd891654c8680c6e9d6584c
New function 'resetCI' resets the CallInfo list of a thread, ensuring
a proper state when creating a new thread, closing a thread, or
closing a state, so that we can run code after that. (When closing a
thread, we need to run its __close metamethods; when closing a
state, we need to run its __close metamethods and its finalizers.)
'luaD_seterrorobj' should not raise errors2025-03-12T18:51:16+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-03-12T18:51:16+00:00urn:sha1:c931d86e98da320c71da70c16d44aa28e9755520
This function can be called unprotected, so it should not raise any
kind of errors. (It could raise a memory-allocation error when creating
a message).
Main thread is a regular field of global_State2025-01-31T16:51:38+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-01-31T16:51:38+00:00urn:sha1:fa1382b5cd504bdfc5fc3f5c447ed09a4c9804fd
They were already allocated as a single block, so there is no need
for the global_State to point to its main thread.
New type 'TStatus' for thread status/error codes2025-01-30T14:41:39+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-01-30T14:41:39+00:00urn:sha1:d1e677c52be3b107a7a29fdc482158f6d9251e79'objsize' returns 'l_mem'2024-11-15T15:04:53+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-11-15T15:04:53+00:00urn:sha1:a4762b6ffe74f5878882ef238d37bfa92d90e418
Sums of size_t may not fit in a size_t.
Small bug in 'luaE_luaE_statesize'2024-10-21T18:30:35+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-10-21T18:30:35+00:00urn:sha1:9b01da97e3a8f2df9acbd3b86af50e4040e9d914
Plus, function was renamed to 'luaE_threadsize'.
'objsize' broke in smaller pieces2024-09-30T17:01:42+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-09-30T17:01:42+00:00urn:sha1:3d54b42d59bcc1b31a369f3497ac22745d63cae6