View Single Post
Old 04-19-2009, 02:32 AM   #11
TriggerHappy
 
Join Date: Feb 2008
Posts: 405

Submissions (2)

TriggerHappy will become famous soon enough (43)TriggerHappy will become famous soon enough (43)

Default

Quote:
Originally Posted by Dark_Dragon
Use Get/SetWidgetLife is slower since it must check what it must do item, unit, destructable to who and how to change a life since in c++ we have classes of unit, destructable and item...

setunitstate knows that it will apply something to unit and in fact getwidgetlife and getunitstate are different getunitstate is a constant native...

and inlining means do not call function but use its actions directly and storing value in local and then destroying it is not a problem its of same speed exept you have to null that local effect but i think he did that so no leaks...

Get widget life has been tested, and is faster.

Just because you assume what goes on in the backend, doesn't make it true.
TriggerHappy is offline   Reply With Quote