lua/ldo.h, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12026-06-03T14:58:39+00:00Removed unused function 'luaD_inctop'2026-06-03T14:58:39+00:00Roberto Iroberto@inf.puc-rio.br2026-06-03T14:58:39+00:00urn:sha1:40b76de2d77e66b70a9d4bf989c3f5340919973f
Commit 3228a97 removed all its uses.
Bug: 'lua_load' does not preserve the stack2026-04-23T20:57:42+00:00Roberto Iroberto@inf.puc-rio.br2026-04-23T20:57:42+00:00urn:sha1:3228a97c6a953dcf397944161bb64b12f1ff5384
'lua_load' does not preserve the stack through the calls to the
reader function, as it should. Immediately after the first call (to
detect whether chunk is binary) it adds stuff, and it also adds a new
table when starting the compilation of each new function.
GC checks stack space before running finalizer2025-12-13T19:16:59+00:00Roberto Iroberto@inf.puc-rio.br2025-12-13T19:16:59+00:00urn:sha1:a5522f06d2679b8f18534fd6a9968f7eb539dc31
If the stack does not have some minimum available space, the GC defers
calling a finalizer until the next cycle. That avoids errors while
running a finalizer 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.
'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).
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:d1e677c52be3b107a7a29fdc482158f6d9251e79Cleaning of llimits.h2024-06-20T16:43:33+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-06-20T16:43:33+00:00urn:sha1:55ac40f859ad8e28fe71a8801d49f4a4140e8aa3
Several definitions that don't need to be "global" (that is, that
concerns only specific parts of the code) moved out of llimits.h,
to more appropriate places.
Merge branch 'master' into nextversion2023-06-22T14:41:48+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-06-22T14:41:48+00:00urn:sha1:ab6a94952215b1f66436d8eeebded1dad9fa5409Several functions turned 'static'2023-05-22T17:47:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-05-22T17:47:54+00:00urn:sha1:9be74ccc214eb6f4d9d0b9496fd973542c7377d9
Several functions that were already being used only inside their
own file have been declared as 'static'.
Removed GC checks from function calls2022-11-24T13:20:15+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-11-24T13:20:15+00:00urn:sha1:152b51955aabb9dfb32302569fac810e999eda03
Function calls do not create new objects. (It may use memory with
stack reallocation, but now that is irrelevant to the GC.)