[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors
- From: Francisco Olarte <folarte@...>
- Date: Tue, 25 Jun 2019 19:30:57 +0200
Sergey:
On Tue, Jun 25, 2019 at 6:25 PM Sergey Kovalev <kovserg33@gmail.com> wrote:
> __unreference should call immediately when reference count to zero,
> unliket __gc it is called latter then there is no way to stand more or
> when explicitly call collectgarbage()
Lua does not work by reference count.
OTOH, <toclose> is really handy to implement your own ref-count
schemes, I'm planning to use it for that if I ever switchto 5.4.
Francisco Olarte.
- References:
- Lua 5.4.0-alpha-rc1 behavior with closing methods errors, phlnc8
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, David Heiko Kolf
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Francisco Olarte
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, David Heiko Kolf
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Francisco Olarte
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, David Heiko Kolf
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Francisco Olarte
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Sergey Kovalev
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Matthew Wild
- Re: Lua 5.4.0-alpha-rc1 behavior with closing methods errors, Sergey Kovalev