lua/manual, branch v5.4.3A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.32021-03-09T14:42:45+00:00lua_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 release number (5.4.3)2021-03-03T12:44:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-03T12:44:20+00:00urn:sha1:e7803f7dbcdc966ab1f9db143424ee811ab1a398Normalization of metamethod typography in the manual2021-03-02T16:50:00+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-02T16:50:00+00:00urn:sha1:b7eb21c1efbd33affb87479fc6055914fe9ab009'__close' methods can yield in the return of a C function2021-02-12T16:36:30+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-12T16:36:30+00:00urn:sha1:bc970005ce2e258e29a5c315ea4e49f76a66586e
When, inside a coroutine, a C function with to-be-closed slots return,
the corresponding metamethods can yield. ('__close' metamethods called
through 'lua_closeslot' still cannot yield, as there is no continuation
to go when resuming.)
Simpler handling of errors when creating tbc variables2021-01-19T13:03:13+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-01-19T13:03:13+00:00urn:sha1:6ccd24eff58340c00db2877c4558a63c6b859442
New field 'lua_State.ptbc' keeps to-be-closed variable until its
upvalue is created, so that it can be closed in case of a
memory-allocation error.
Corrected documentation for 'table.sort'2021-01-14T16:26:55+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-01-14T16:26:55+00:00urn:sha1:825ac8eca8e384d6ad2538b5670088c31e08a9d7
The sort function must define a (strict) weak order for a correct
sorting. A partial order is not enough.
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.
Report last error in closing methods2020-12-22T13:54:25+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-22T13:54:25+00:00urn:sha1:0ceada8da92135717d31a3954b5b89a954f9e71a
When there are multiple errors around closing methods, report the
last error instead of the original.
Upvalues removed from 'openupval' before being closed2020-12-21T18:21:45+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-21T18:21:45+00:00urn:sha1:f9d29b0c442447ebe429bcaad1e2b4bf13c5dc93
Undo commit c220b0a5d0: '__close' is not called again in case of
errors. (Upvalue is removed from the list before the call.) The
common error that justified that change was C stack overflows, which
are much rarer with the stackless implementation.
'coroutine.close'/'lua_resetthread' report original errors2020-12-18T14:22:42+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-18T14:22:42+00:00urn:sha1:409256b7849ec5ab3296cb0ab9eba3d65955d5ea
Besides errors in closing methods, 'coroutine.close' and
'lua_resetthread' also consider the original error that stopped the
thread, if any.