TimerUtils

[DracoL1ch]

Is there any reason why this lib is stil a thing?
"pro": instead of creating object you check for the one of pre-created group, which perfomance-wise better.
Reality: any operation in JASS takes ages comparing to engine's workout, and timers are also the most light-weight object of the whole game. Even a single compare will kill all the purpose of this nitpicking, not to speak you also have to return value.

"pro": you can attach a single integer data inside the timer with 1 func.
Reality: you can do that via tons of other stuff, which barely makes any difference, as it's still dirty hack and not perfomance trick.

So what the point?

 

[Flux]

Well it is easier to write

//Start
call TimerStart(NewTimerEx(this), 1.0, false, function thistype.onPeriod)
//Retrieve
local thistype this = ReleaseTimer(GetExpiredTimer())

than

//Start
set t = CreateTimer()
set thistype.tb[GetHandleId(t)] = this  //Table
call TimerStart(t, 1.0, false, function thistype.onPeriod)
set t = null
//Retrieve
local timer t = GetExpiredTimer()
local integer id = GetHandleId(t)
local thistype this = thistype.tb[id] //Table
call thistype.tb.remove(id)
call DestroyTimer(t)
set t = null

What the point? convenience.
Does it make a difference performance-wise? No, I think it's negligible
Hotel? Trivago

 

[btdonald]

TimerUtils has its own limit (256 instance)

 

[AGD]

local thistype this = ReleaseTimer(GetExpiredTimer())
ReleaseTimer() returns timer data?

 

[Flux]

In TimerUtilsEx (which I uses), it does. In fact that's the reason why I uses that instead of the original.

 

[btdonald]

local thistype this = ReleaseTimer(GetExpiredTimer())
ReleaseTimer() returns timer data?

With TimerUtilsEx, ReleaseTimer() return Data.