<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/testes/utf8.lua, 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>2023-08-17T13:42:56+00:00</updated>
<entry>
<title>More control over encoding of test files</title>
<updated>2023-08-17T13:42:56+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2023-08-17T13:42:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=f4211a5ea4e235ccfa8b8dfa46031c23e9e839e2'/>
<id>urn:sha1:f4211a5ea4e235ccfa8b8dfa46031c23e9e839e2</id>
<content type='text'>
The few UTF-8 test files are commented as such, and there is only one
non UTF-8 test file (to test non UTF-8 sources).
</content>
</entry>
<entry>
<title>Avoid excessive name pollution in test files</title>
<updated>2022-12-28T21:34:11+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2022-12-28T21:34:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=314745ed8438d1276c6c928d5f9d4be018dfadb6'/>
<id>urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6</id>
<content type='text'>
Test files are more polite regarding the use of globals when locals
would do, and when globals are necessary deleting them after use.
</content>
</entry>
<entry>
<title>Bug: 'utf8.codes' accepts spurious continuation bytes</title>
<updated>2022-09-23T13:41:16+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2022-09-23T13:41:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=a1089b415a3f5c753aa1b40758ffdaf28d5701b0'/>
<id>urn:sha1:a1089b415a3f5c753aa1b40758ffdaf28d5701b0</id>
<content type='text'>
</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>Details (more uniformity in error messages)</title>
<updated>2020-05-27T14:46:47+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2020-05-27T14:46:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=aa8d4a782d88738b3ea921cde5a450656da8fa63'/>
<id>urn:sha1:aa8d4a782d88738b3ea921cde5a450656da8fa63</id>
<content type='text'>
</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>Fixed wrong error message in 'return math.seed(0)'</title>
<updated>2019-04-04T19:31:24+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-04-04T19:31:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=8004798b0374744208b102bb4cbcf12f904ea120'/>
<id>urn:sha1:8004798b0374744208b102bb4cbcf12f904ea120</id>
<content type='text'>
Bug introduced in commit 28d829c8: OP_TAILCALL might raise an
error without saving 'pc'. (This commit also fixes a detail in
'testes/uf8.lua'.)
</content>
</entry>
<entry>
<title>Small optimizations in range checks</title>
<updated>2019-03-27T17:56:10+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-03-27T17:56:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=d12262068d689eacc452a459a021df0ad8f6d46c'/>
<id>urn:sha1:d12262068d689eacc452a459a021df0ad8f6d46c</id>
<content type='text'>
Checks of the form '1 &lt;= x &amp;&amp; x &lt;= M' were rewritten in the form
'(unsigned)x - 1 &lt; (unsigned)M', which is usually more efficient.
(Other similar checks have similar translations.) Although
some compilers do these optimizations, that does not happen
for all compilers or all cases.
</content>
</entry>
<entry>
<title>Changes in the validation of UTF-8</title>
<updated>2019-03-15T16:14:17+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2019-03-15T16:14:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=1e0c73d5b643707335b06abd2546a83d9439d14c'/>
<id>urn:sha1:1e0c73d5b643707335b06abd2546a83d9439d14c</id>
<content type='text'>
All UTF-8 encoding functionality (including the escape
sequence '\u') accepts all values from the original UTF-8
specification (with sequences of up to six bytes).

By default, the decoding functions in the UTF-8 library do not
accept invalid Unicode code points, such as surrogates. A new
parameter 'nonstrict' makes them accept all code points up to
(2^31)-1, as in the original UTF-8 specification.
</content>
</entry>
<entry>
<title>Added directory to test file names in '$Id:'</title>
<updated>2018-07-25T18:31:04+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2018-07-25T18:31:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=aa4c5cf190f77ab2730af5e21cfd2b830ff329df'/>
<id>urn:sha1:aa4c5cf190f77ab2730af5e21cfd2b830ff329df</id>
<content type='text'>
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'.
</content>
</entry>
</feed>
