[Trigger] Epic Question Time! Which is better?

[Marsal]

What if you made a spell that uses an indexing system and it lasts for e.q. 5 seconds. Which one would you prefer to store a position? The caster unit won't move away.

1. Store the position at the beginning of the spell and remove it at the end. (Less function calls but an extra variable)
2. Every 0.03 second store the position to a temporary variable then remove it.(More function calls but no extra variable)

 

[Geries]

If that lasts for so much time( 5 secs ) then I'd prefer globals or hashtables. Other way needs repetative local calling, nulling, handle destroying etc.

 

[Maker]

Number one. Avoiding unneeded function calls.

 

[Marsal]

Thanks.

 

[defskull]

The reason why you should favor number 1 is because you are using the same point over and over again so that's why you don't need a creating of point variable per each interval, it's like you plant a seed at a same location over and over again.

 

[shadowvzs]

What if you made a spell that uses an indexing system and it lasts for e.q. 5 seconds. Which one would you prefer to store a position? The caster unit won't move away.

1. Store the position at the beginning of the spell and remove it at the end. (Less function calls but an extra variable)
2. Every 0.03 second store the position to a temporary variable then remove it.(More function calls but no extra variable)

1. but i prefer the 2 real variables instead 1 location coz i heard its faster, coz -1 function call (dont need convert coord to point Location(x,y)), index the unit custom value if u cant cast again before effect over

else i think hashtable also good and timerid or something unique the key1, then example could be like this savereal (hashtable, timerid, 1, x),savereal (hashtable, timerid, 2, y)