<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/lbaselib.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-12-13T13:41:17+00:00</updated>
<entry>
<title>Bug: GC is not reentrant</title>
<updated>2021-12-13T13:41:17+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-12-13T13:41:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=0bfc572e51d9035a615ef6e9523f736c9ffa8e57'/>
<id>urn:sha1:0bfc572e51d9035a615ef6e9523f736c9ffa8e57</id>
<content type='text'>
As the GC is not reentrant, finalizers should not be able to invoke it.
</content>
</entry>
<entry>
<title>Avoid overflows when incrementing parameters in C</title>
<updated>2021-09-22T16:10:39+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-09-22T16:10:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=deac067ed39a44c001599c0d15de09872496b2aa'/>
<id>urn:sha1:deac067ed39a44c001599c0d15de09872496b2aa</id>
<content type='text'>
Any C function can receive maxinteger as an integer argument, and
therefore cannot increment it without some care (e.g., doing unsigned
arithmetic as the core does).
</content>
</entry>
<entry>
<title>Allow yields inside '__pairs'</title>
<updated>2021-03-29T15:57:32+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-03-29T15:57:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=bf10593a3a912cd3cac69569c7474e687c0d0cd8'/>
<id>urn:sha1:bf10593a3a912cd3cac69569c7474e687c0d0cd8</id>
<content type='text'>
</content>
</entry>
<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>Janitorial work</title>
<updated>2021-01-25T13:39:18+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-01-25T13:39:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=1f81baffadad9d955b030a1a29b9b06042a66552'/>
<id>urn:sha1:1f81baffadad9d955b030a1a29b9b06042a66552</id>
<content type='text'>
Comments, code details, identation.
</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>
<entry>
<title>Added control messages to warnings</title>
<updated>2019-08-15T16:44:36+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-08-15T16:44:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=a1d8eb27431c02c4529be1efd92143ad65434f3a'/>
<id>urn:sha1:a1d8eb27431c02c4529be1efd92143ad65434f3a</id>
<content type='text'>
Added the concept of control messages to the warning system, plus the
implementation of the controls "@on"/"@off" to turn warnings on/off.
Moreover, the warning system in the test library adds some other
controls to ease the test of warnings.
</content>
</entry>
<entry>
<title>Function 'warn' is vararg</title>
<updated>2019-06-04T14:22:21+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-06-04T14:22:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=14edd364c3abcb758e74c68a2bdd4ddaeefdae2a'/>
<id>urn:sha1:14edd364c3abcb758e74c68a2bdd4ddaeefdae2a</id>
<content type='text'>
Instead of a 'tocont' flag, the function 'warn' in Lua now receives all
message pieces as multiple arguments in a single call. Besides being
simpler to use, this implementation ensures that Lua code cannot create
unfinished warnings.
</content>
</entry>
<entry>
<title>'print' does not call 'tostring' to format its arguments</title>
<updated>2019-04-10T15:58:14+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-04-10T15:58:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=8ba4523cccf59093543cec988b07957193d55692'/>
<id>urn:sha1:8ba4523cccf59093543cec988b07957193d55692</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Changes in the warning system</title>
<updated>2019-03-14T18:30:54+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-03-14T18:30:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=b56d4e570a60a8e84df8288c3122eb5bb5c20af6'/>
<id>urn:sha1:b56d4e570a60a8e84df8288c3122eb5bb5c20af6</id>
<content type='text'>
- The warning functions get an extra parameter that tells whether
message is to be continued (instead of using end-of-lines as a signal).

- The user data for the warning function is a regular value, instead
of a writable slot inside the Lua state.
</content>
</entry>
</feed>
