lua/testes/vararg.lua, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12025-11-26T14:18:29+00:00New 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.
Vertical bar removed from syntax of vararg table2025-10-30T14:07:01+00:00Roberto Iroberto@inf.puc-rio.br2025-10-30T14:07:01+00:00urn:sha1:d342328e5b24c9b3c6c5b33bfcf9f8534210b8e6
The syntax 'function foo (a, b, ...arg)' is already used by JavaScript
for this same semantics, so it seems natural to use the same notation in
Lua.
Case VVARGIND added to luaK_storevar2025-10-30T13:39:55+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-10-30T13:39:55+00:00urn:sha1:0149b781d438091ce086449101a916e9b4456b4e
In a global initialization, the variable does not pass through
'check_readonly', and therefore a VVARGIND is not normalized to a
VINDEXED.
Optimization for vararg tables2025-09-24T21:33:08+00:00Roberto Iroberto@inf.puc-rio.br2025-09-24T21:33:08+00:00urn:sha1:25c54fe60e22d05cdfaa48c64372d354efa59547
A vararg table can be virtual. If the vararg table is used only as
a base in indexing expressions, the code does not need to create an
actual table for it. Instead, it compiles the indexing expressions
into direct accesses to the internal vararg data.
Varag parameter is a new kind of variable2025-09-17T19:07:48+00:00Roberto Iroberto@inf.puc-rio.br2025-09-17T19:07:48+00:00urn:sha1:8fb1af0e33cd8688f57cd0e3ab86420a8cfe99bd
To allow some optimizations on its use.
Vararg table2025-09-16T16:26:24+00:00Roberto Iroberto@inf.puc-rio.br2025-09-16T16:26:24+00:00urn:sha1:140b672e2ee2ac842661ece4b48e1a64f0cd11ea
Not yet optimized nor documented.
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'.
Avoid excessive name pollution in test files2022-12-28T21:34:11+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-12-28T21:34:11+00:00urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6
Test files are more polite regarding the use of globals when locals
would do, and when globals are necessary deleting them after use.
Added directory to test file names in '$Id:'2018-07-25T18:31:04+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2018-07-25T18:31:04+00:00urn:sha1:aa4c5cf190f77ab2730af5e21cfd2b830ff329df
From the point of view of 'git', all names are relative to the root
directory of the project. So, file names in '$Id:' also should be
relative to that directory: the proper name for test file 'all.lua'
is 'testes/all.lua'.
Added manual and tests for version 5.4-w22018-07-09T15:33:01+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2018-07-09T15:33:01+00:00urn:sha1:7c519dfbd0c68b952f0849e01deaa3750e1f8153