What ever happened to this as a viable option?
as compared to T32, which has, per timer expiration, a (trigger evaluate)+(function call/instance). In the periodic method, it loops through current instances, and swaps in place the next instance if the current instance is over.
in the aforementioned TimedLoop module, for each timer expiration, you have (function call/instance). It loops through each instance periodically and swaps the last in for the current when that instance is over.
the only thing I can see as being an improvement is the fact that T32 has slightly less overhead in the loop function (the heaviest of which being simple arithmetic), since it uses a function call to remove instances, rather than a boolean return from that instances function call, but then again there is also the added triggerevaluate.
anywho - does this make that large a difference in performance - or is there something else I am totally missing?
as compared to T32, which has, per timer expiration, a (trigger evaluate)+(function call/instance). In the periodic method, it loops through current instances, and swaps in place the next instance if the current instance is over.
in the aforementioned TimedLoop module, for each timer expiration, you have (function call/instance). It loops through each instance periodically and swaps the last in for the current when that instance is over.
the only thing I can see as being an improvement is the fact that T32 has slightly less overhead in the loop function (the heaviest of which being simple arithmetic), since it uses a function call to remove instances, rather than a boolean return from that instances function call, but then again there is also the added triggerevaluate.
anywho - does this make that large a difference in performance - or is there something else I am totally missing?