lua/testes/db.lua, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12025-11-28T18:12:51+00:00Functions with vararg tables don't need hidden args.2025-11-28T18:12:51+00:00Roberto Iroberto@inf.puc-rio.br2025-11-28T18:12:51+00:00urn:sha1:a07f6a824197d7dc01c321599d3bc71936a2590e
Vararg functions with vararg tables don't use the arguments hidden in
the stack; therfore, it doesn't need to build/keep them.
New conceptual model for vararg2025-11-26T14:18:29+00:00Roberto Iroberto@inf.puc-rio.br2025-11-26T14:18:29+00:00urn:sha1:f33cc4ddec886ea499d7d41dd60cac5ddc5687db
Conceptually, all functions get their vararg arguments in a vararg
table. The storing of vararg arguments in the stack is always treated
as an optimization.
New way to control preambular declaration2025-05-20T20:36:05+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-05-20T20:36:05+00:00urn:sha1:be05c444818989463dc307eed283503d391f93eb
Validity of the preambular global declaration in controled together
with all declarations, when checking variable names.
First implementation of global declarations2025-05-05T19:24:59+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-05-05T19:24:59+00:00urn:sha1:be8120906304a8658fab998587b969e0e42f5650Details (typos in comments)2025-04-23T14:36:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-04-23T14:36:09+00:00urn:sha1:9b014d4bcd4ebadb523f1c1a1d38148d8526e5edOrder change in 'pushfuncname'2025-04-03T18:31:22+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-04-03T18:31:22+00:00urn:sha1:3dd8ea54daa77345a8f193e871f6792722d8e131
'pushglobalfuncname' can be quite slow (as it traverses all globals and
all loaded modules), so try first to get a name from the code.
Removed copyright notice from 'testes/all.lua'2025-03-12T17:00:58+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-03-12T17:00:58+00:00urn:sha1:ab66652b3270b95222dea134b5e47bb3afc434cc
All test files refer to the main copyright notice in 'lua.h'.
Another way to compile goto's2025-01-10T16:54:51+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-01-10T16:54:51+00:00urn:sha1:7ca3c40b50b385ead6b8bc4c54de97b61d11a12a
The compilation of a goto or a label just create an entry and generate
boilerplate code for the gotos. As we don't know yet whether it needs a
CLOSE, we code a jump followed by a CLOSE, which is then dead code.
When a block ends (and then we know for sure whether there are variables
that need to be closed), we check the goto's against the labels of that
block. When closing a goto against a label, if it needs a CLOSE, the
compiler swaps the order of the jump and the CLOSE, making the CLOSE
active.
Debug information about extra arguments from __call2024-11-19T17:09:18+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-11-19T17:09:18+00:00urn:sha1:50c7c915ee2fa239043d5456237f5145d064089b
'debug.getinfo' can return number of extra arguments added to a call by
a chain of __call metavalues. That information is being used to improve
error messages about errors in these extra arguments.
Bug: Active-lines for stripped vararg functions2024-06-04T20:27:13+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-06-04T20:27:13+00:00urn:sha1:bdc85357aa41a9610498232c2cffe7aa191e5cf6
Lua seg. faults when asked to create the 'activelines' table for a
vararg function with no debug information.