lua, branch =listA mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=%3Dlist2025-06-23T17:36:32+00:00Application name for 'readline' is "lua", not "Lua"2025-06-23T17:36:32+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-23T17:36:32+00:00urn:sha1:270a58c0629dea1a376f05433e8df383756173a8Refactoring in the use of 'readline' by 'lua.c'2025-06-23T17:00:21+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-23T17:00:21+00:00urn:sha1:30531c291b25243e05a9734033a6a023c18f13ac
More common code for 'readline' loaded statically or dynamically (or
not loaded).
No need to limit variable declarations to 2502025-06-18T19:45:55+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-18T19:45:55+00:00urn:sha1:07b009c3712c062957593d0a4fa82e0fe9023024
Only local variables, which use registers, need this low limit.
Check string indices when loading binary chunk2025-06-17T14:40:49+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-17T14:40:49+00:00urn:sha1:f71156744851701b5d5fabdda5061b31e53f8f14
Lua is not religious about that, but it tries to avoid crashes when
loading binary chunks.
New metatable in an all-weak table can fool the GC2025-06-16T19:29:32+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-16T19:29:32+00:00urn:sha1:9386e49a3173b68e8b5a7ba882c4c2faf557b61e
All-weak tables are not being revisited after being visited during
propagation; if it gets a new metatable after that, the new metatable
may not be marked.
Simpler code for 'traversetable'2025-06-16T18:50:12+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-16T18:50:12+00:00urn:sha1:8cd7ae7da06f54b97f95d6994d6bf47086e4e7eb
Check the mode in a separate function (getmode), instead of using
comma expressions inside the 'if' condition.
Dump uses varints also for integer constants2025-06-13T17:14:50+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-13T17:14:50+00:00urn:sha1:0cecf1ab6d76e6a7d200fb01bdd999b61835fe21
Unlike sizes, these constants can be negative, so it encodes those
integers into unsigned integers in a way that keeps small numbers
small.
The main thread cannot be closed2025-06-13T17:08:38+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-13T17:08:38+00:00urn:sha1:e657a48ea5698bbd9982d878eb65e6615ec94f7e
No thread started with pcall (instead of resume) can be closed,
because coroutine.close would not respect the expected number of
results from the protected call.
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.
Loading a binary chunk should not break assertions2025-06-04T15:55:43+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-04T15:55:43+00:00urn:sha1:d05fe48bfdd89956c0ebd115dca0fb115aa28dd6
Although the execution of a bad binary chunk can crash the interpreter,
simply loading it should be safe.