<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/ldblib.c, branch v5.4.9</title>
<subtitle>A mirror of https://github.com/lua/lua
</subtitle>
<id>https://git.lua4.win/lua/atom?h=v5.4.9</id>
<link rel='self' href='https://git.lua4.win/lua/atom?h=v5.4.9'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/'/>
<updated>2021-02-24T14:14:44+00:00</updated>
<entry>
<title>Broadening the use of branch hints</title>
<updated>2021-02-24T14:14:44+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-02-24T14:14:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=59c88f846d1dcd901a4420651aedf27816618923'/>
<id>urn:sha1:59c88f846d1dcd901a4420651aedf27816618923</id>
<content type='text'>
More uses of macros 'likely'/'unlikely' (renamed to
'l_likely'/'l_unlikely'), both in range (extended to the
libraries) and in scope (extended to hooks, stack growth).
</content>
</entry>
<entry>
<title>Bug: cannot allow the call 'debug.getinfo(0, "&gt;")'</title>
<updated>2021-02-15T13:38:09+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-02-15T13:38:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=38cc7d40a4bcb89314d212fdffd2ca8deebc3cb7'/>
<id>urn:sha1:38cc7d40a4bcb89314d212fdffd2ca8deebc3cb7</id>
<content type='text'>
A 'what' argument starting with '&gt;' indicates that there is a function
in the C stack, which won't be there if the first argument is not a
function.
</content>
</entry>
<entry>
<title>Details</title>
<updated>2020-12-02T18:13:13+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-12-02T18:13:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d9d2904f09a8039522dfd6f118d4e37bffd5bdf6'/>
<id>urn:sha1:d9d2904f09a8039522dfd6f118d4e37bffd5bdf6</id>
<content type='text'>
Names in the parser and other details that do not change actual code.
</content>
</entry>
<entry>
<title>'lua_upvalueid' returns NULL on invalid upvalue index</title>
<updated>2020-10-12T17:51:28+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-10-12T17:51:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=30528049f1d11ea2854a6431e8e8524f83206559'/>
<id>urn:sha1:30528049f1d11ea2854a6431e8e8524f83206559</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revision of stackless implementation</title>
<updated>2020-10-12T15:29:09+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-09-23T13:18:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=287b302acb8d925178e9edb800f0a8d18c7d35f6'/>
<id>urn:sha1:287b302acb8d925178e9edb800f0a8d18c7d35f6</id>
<content type='text'>
- more organized handling of 'nCcalls'
- comments
- deprecation of 'setcstacklimit'
</content>
</entry>
<entry>
<title>Avoid calling 'fprintf' with NULL</title>
<updated>2020-06-09T19:12:01+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-06-09T19:12:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=364e569945c044fd18c70ee1bc851364534aef97'/>
<id>urn:sha1:364e569945c044fd18c70ee1bc851364534aef97</id>
<content type='text'>
Avoid undefined behavior in calls like «fprintf("%s", NULL)».
('lua_writestringerror' is implemented as 'fprintf', and 'lua_tostring'
can return NULL if object is not a string.)
</content>
</entry>
<entry>
<title>Details</title>
<updated>2020-02-27T15:59:22+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-02-27T15:59:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=6eb53b752617fae9e1329bfe2cfecdcbb593c398'/>
<id>urn:sha1:6eb53b752617fae9e1329bfe2cfecdcbb593c398</id>
<content type='text'>
Several details in code (e.g., moving a variable to the most inner
scope that encloses its uses), comments, parameter names, extra tests.
</content>
</entry>
<entry>
<title>Fixed a warning and other minor issues</title>
<updated>2019-10-04T19:17:04+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-10-04T19:17:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=7bd1e53753de7176eb0b23f2bf19ad2235dec826'/>
<id>urn:sha1:7bd1e53753de7176eb0b23f2bf19ad2235dec826</id>
<content type='text'>
Fixed some minor issues from the feedback for 5.4-beta rc1.
</content>
</entry>
<entry>
<title>'setCstacklimit' renamed to 'setcstacklimit'</title>
<updated>2019-09-24T17:31:06+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-09-24T17:31:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=03cde80b58ea7f112f1b7a35c037893093b59f2e'/>
<id>urn:sha1:03cde80b58ea7f112f1b7a35c037893093b59f2e</id>
<content type='text'>
Function names in the API use only lowercase letters.
</content>
</entry>
<entry>
<title>Added macro 'luaL_pushfail'</title>
<updated>2019-08-16T17:58:02+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-08-16T17:58:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=b96b0b5abbf40cbdbed7952bf35a5a27ddf75928'/>
<id>urn:sha1:b96b0b5abbf40cbdbed7952bf35a5a27ddf75928</id>
<content type='text'>
The macro 'luaL_pushfail' documents all places in the standard libraries
that return nil to signal some kind of failure. It is defined as
'lua_pushnil'. The manual also got a notation (@fail) to document those
returns. The tests were changed to be agnostic regarding whether 'fail'
is 'nil' or 'false'.
</content>
</entry>
</feed>
