Memory leak questions

[AoW_Hun7312]

I was reading up on memory leaks using the tutorials here, and ran into a few questions.

1. Do I have to null local player variables? What else has to be nulled?

2. Do I have to create a "fake" boolexpr in this function, or am I fine using null?

call TriggerRegisterPlayerUnitEvent(t, Player(i), EVENT_PLAYER_UNIT_ATTACKED, null

 

[saw792]

1. No, You null types that extend agent in common.j
2. No

 

[kingkingyyk3]

Just use null, bliz fixed that.

 

[BlueMirage]

I also have a question regarding memory leaks.

Do you have to null variables that aren't created in the function? By these, I mean taken values. Example:

function DoNull takes nothing returns nothing
    local unit u = udg_SomeUnit //Needs to be nulled
    set u =null
endfunction

function ShouldThisGetNulled takes unit u returns nothing
    set u = null //Is this neccesary???
endfunction

 

[Ayanami]

I also have a question regarding memory leaks.

Do you have to null variables that aren't created in the function? By these, I mean taken values. Example:

function DoNull takes nothing returns nothing
    local unit u = udg_SomeUnit //Needs to be nulled
    set u =null
endfunction

function ShouldThisGetNulled takes unit u returns nothing
    set u = null //Is this neccesary???
endfunction

No, you won't need to null that.

 

[kingkingyyk3]

Parameter are automatically nulled.

 

[Azlier]

Parameter are automatically nulled.

Indeed. The only reason we have to null local variables anyway is because of a bug.

 

[Bribe]

Due to JASS being an interpreter and not a truly compiled language, a lot of things happen behind the scenes.

The 'set' keyword gets hooked by the game engine during application runtime, for example. 'set' in JASS is much slower than most languages because of this. The hook makes it so variables set to handles are 'smart' and remember the handle id even if the object itself is destroyed.