<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/testes, branch rc</title>
<subtitle>A mirror of https://github.com/lua/lua
</subtitle>
<id>https://git.lua4.win/lua/atom?h=rc</id>
<link rel='self' href='https://git.lua4.win/lua/atom?h=rc'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/'/>
<updated>2025-11-28T18:12:51+00:00</updated>
<entry>
<title>Functions with vararg tables don't need hidden args.</title>
<updated>2025-11-28T18:12:51+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-28T18:12:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=a07f6a824197d7dc01c321599d3bc71936a2590e'/>
<id>urn:sha1:a07f6a824197d7dc01c321599d3bc71936a2590e</id>
<content type='text'>
Vararg functions with vararg tables don't use the arguments hidden in
the stack; therfore, it doesn't need to build/keep them.
</content>
</entry>
<entry>
<title>New conceptual model for vararg</title>
<updated>2025-11-26T14:18:29+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-26T14:18:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=f33cc4ddec886ea499d7d41dd60cac5ddc5687db'/>
<id>urn:sha1:f33cc4ddec886ea499d7d41dd60cac5ddc5687db</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Details</title>
<updated>2025-11-24T14:39:46+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-24T14:39:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d94f7ba3040eb06895d7305014e88157d3bfd1a1'/>
<id>urn:sha1:d94f7ba3040eb06895d7305014e88157d3bfd1a1</id>
<content type='text'>
Comments, capitalization in the manual, globals in test 'heady.lua'
</content>
</entry>
<entry>
<title>'__pairs' can also return a to-be-closed object</title>
<updated>2025-11-11T18:11:06+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-11T18:11:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=4cf498210e6a60637a7abb06d32460ec21efdbdc'/>
<id>urn:sha1:4cf498210e6a60637a7abb06d32460ec21efdbdc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>External strings are as good as internal ones</title>
<updated>2025-11-11T17:40:30+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-11T17:40:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=5b7d9987642f72d44223a8e5e79e013bb2b3d579'/>
<id>urn:sha1:5b7d9987642f72d44223a8e5e79e013bb2b3d579</id>
<content type='text'>
A '__mode' metafield and an "n" key both can be external strings.
</content>
</entry>
<entry>
<title>Correction in line info for semantic errors</title>
<updated>2025-11-11T17:36:16+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-11T17:36:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=81f4def54f440e045b1401f11ef78b65b56b7abe'/>
<id>urn:sha1:81f4def54f440e045b1401f11ef78b65b56b7abe</id>
<content type='text'>
Semantic errors should refer the last used token, not the next one.
</content>
</entry>
<entry>
<title>Global initialization checks name conflict</title>
<updated>2025-11-08T14:43:42+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-11-08T14:43:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=e44f3a2ffc7ced5e75cca7657aaa60ef27da89aa'/>
<id>urn:sha1:e44f3a2ffc7ced5e75cca7657aaa60ef27da89aa</id>
<content type='text'>
Initialization "global a = 10" raises an error if global 'a' is already
defined, that is, it has a non-nil value.
</content>
</entry>
<entry>
<title>Vertical bar removed from syntax of vararg table</title>
<updated>2025-10-30T14:07:01+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-10-30T14:07:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d342328e5b24c9b3c6c5b33bfcf9f8534210b8e6'/>
<id>urn:sha1:d342328e5b24c9b3c6c5b33bfcf9f8534210b8e6</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Case VVARGIND added to luaK_storevar</title>
<updated>2025-10-30T13:39:55+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-10-30T13:39:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=0149b781d438091ce086449101a916e9b4456b4e'/>
<id>urn:sha1:0149b781d438091ce086449101a916e9b4456b4e</id>
<content type='text'>
In a global initialization, the variable does not pass through
'check_readonly', and therefore a VVARGIND is not normalized to a
VINDEXED.
</content>
</entry>
<entry>
<title>Fixed initialization of global variables</title>
<updated>2025-10-29T16:14:48+00:00</updated>
<author>
<name>Roberto I</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-10-29T16:14:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d4eff00234dc55dac4cb86b6187f5607c1254f9b'/>
<id>urn:sha1:d4eff00234dc55dac4cb86b6187f5607c1254f9b</id>
<content type='text'>
When calling 'luaK_storevar', the 'expdesc' for the variable must be
created before the one for the expression, to satisfy the assumptions
for register allocation. So, in a statement like 'global a = exp', where
'a' is actually '_ENV.a', this variable must be handled before the
initializing expression 'exp'.
</content>
</entry>
</feed>
