Is ok that LLTimers.every() throws errors as 'on'?
complete
SuzannaLinn Resident
Internally there is only LLTimers:on(), but it could be confusing for beginners:
LLTimers.every(1, print) -- with a point
-- > invalid argument #1 to 'on' (LLTimers expected, got number)
LLTimers:every(1, myUndefFunc)
-- > invalid argument #3 to 'on' (function or callable table expected, got nil)
If :every() is the prefered one, could the internal function be every() instead of on()?
Log In
H
Harold Linden
marked this post as
complete
Should be fixed now that
LLTimers:on()
is removed, thanks again!H
Harold Linden
marked this post as
in progress
I just realized this is already implicitly fixed by a SLua change I made a few days ago, this'll be fixed in the next release!
H
Harold Linden
I'm just going to remove
:on()
since there's not a good use-case for having the alias now that we've decided :every()
is a better name.H
Harold Linden
marked this post as
planned
We'll get this fixed up, thanks for the report!