Nulling Locals

[Carl-Fredrik]

Hi everyone.. I was wondering, I have this trigger that spawns units and sends them away. It runs each 30 second and has two local locations involved (Create them at loc and send them to loc)

So I was wondering, shall I (set null) / (call RemoveLocation) these to prevent leaks? Or will it only work once then?

Thanks in advance!
// Carl-Fredrik

 

[phyrex1an]

Hi everyone.. I was wondering, I have this trigger that spawns units and sends them away. It runs each 30 second and has two local locations involved (Create them at loc and send them to loc)

So I was wondering, shall I (set null) / (call RemoveLocation) these to prevent leaks? Or will it only work once then?

Thanks in advance!
// Carl-Fredrik

You should only remove the locations if you create them in that trigger. If you create the locations once, eg at map initialization, then you shouldn't remove them.
Posting the code is an easy way to get more specific answers

 

[Tom Jones]

You should always null your local variables, with the exception of integers, reals, booleans, strings, and static pointers. What is a static pointer? All variables point to something, and that something may exist throughout the entire game, and is thus static. Players are an example of this, and yet another example:

globals
    timer T = CreateTimer()
endglobals

function ...
    local timer t = T //We don't have to null this local.
                             
    //We could of course simply reference the global directly, and thus make the above local obsolete.
endfunction

Whenever you create something it should be destroyed. Once again the static rule apply, no need to destroy something the exist throughout the entire game.

 

[Carl-Fredrik]

Ok. Thanks.