[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Can't interrupt tight loops in Lua 5.4 anymore?
- From: Roberto Ierusalimschy <roberto@...>
- Date: Mon, 18 May 2020 14:59:16 -0300
> It may indeed have been a new question, but the question was about "a loop
> _in pure lua code_ that does not ever call a hook
> function", not about signals. And I believe the question can be qualified
> further so that the "pure Lua code" does not directly or indirectly call
> any library, including built-in library, code. The only permissible
> "native" code would be Lua itself (without libs) and the (custom) memory
> allocator. Assuming the latter is always bounded, the expected answer is
> that "eventually a hook function will be called" - is that the case in Lua
> 5.4?
If there are no signals, then there are two cases:
- there was already a line hook set when the loop starts
- there was no hook when the loop starts
For the first case, Lua will eventually call the hook; for the second
case, Lua will never call the (inexistent) hook.
-- Roberto
_______________________________________________
lua-l mailing list -- lua-l@lists.lua.org
To unsubscribe send an email to lua-l-leave@lists.lua.org