lua/testes/api.lua, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92025-01-16T19:25:11+00:00Bug: Missing error status in panic function2025-01-16T19:25:11+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-01-16T19:25:11+00:00urn:sha1:f5e55be2a0ce64066c1b0554675633b92c91fafb
'luaD_throw' may call 'luaE_resetthread', which returns an error code
but clears 'L->status'; so, 'luaD_throw' should set that status again.
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.
Bug: GC is not reentrant2021-12-13T13:41:17+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-12-13T13:41:17+00:00urn:sha1:0bfc572e51d9035a615ef6e9523f736c9ffa8e57
As the GC is not reentrant, finalizers should not be able to invoke it.
lua_settop/lua_pop closes to-be-closed variables2021-03-09T14:42:45+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-09T14:42:45+00:00urn:sha1:511d53a826760dd11cd82947184583e2d094e2d2
The existence of 'lua_closeslot' is no reason for lua_pop not to close
to-be-closed variables too. It is too error-prone for lua_pop not to
close tbc variables being popped from the stack.
New API function 'lua_closeslot'2021-01-11T18:03:01+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-01-11T18:03:01+00:00urn:sha1:cc1692515e2a6aabc6d07159e7926656e38eda53
Closing a to-be-closed variable with 'lua_settop' is too restrictive,
as it erases all slots above the variable. Moreover, it adds side
effects to 'lua_settop', which should be a fairly basic function.
Keep memory errors as memory errors2020-07-06T15:09:44+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-06T15:09:44+00:00urn:sha1:b57574d6fb9071b2f8f261b32c9378ed72db7023
Allow memory errors to be raised through the API (throwing the
error with the memory error message); error in external allocations
raises a memory error; memory errors in coroutines are re-raised
as memory errors.
Comments (mosty typos)2019-12-30T14:45:08+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-12-30T14:45:08+00:00urn:sha1:bd1b87c5790c0c6fe23f76aa360e879922e1e738Joined common code in 'lua_rawset' and 'lua_rawsetp'2019-12-17T18:45:13+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-12-17T18:45:13+00:00urn:sha1:c646e57fd6307bd891e4e50ef5d6ee56b34e4cacAdded macro 'luaL_pushfail'2019-08-16T17:58:02+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-16T17:58:02+00:00urn:sha1:b96b0b5abbf40cbdbed7952bf35a5a27ddf75928
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'.
Added control messages to warnings2019-08-15T16:44:36+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-08-15T16:44:36+00:00urn:sha1:a1d8eb27431c02c4529be1efd92143ad65434f3a
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.