Calling functions that return handles

[sethmachine]

Hi,

I was curious if when one calls a function that returns a handle, does that cause a leak, or does the game know to destroy that handle automatically (since it's not being stored in any variable outside the function because our function is preceded by a call)

Here is an example.

function foo takes nothing returns rect
  return Rect(0.00, 0.00, 0.00, 0.00)
endfunction
...
call foo() //is there now a leaked rect handle in the map?
...
local rect r
set r = foo() //do I need it this way?
call RemoveRect(r)
set r = null

 

[Adiktuz]

I think it will still leak (the first method)... AFAIK, wc3 does not have a nice garbage collector if there is even any...

 

[TriggerHappy]

Yeah it leaks because you don't destroy therectfoo() creates.

 

[BPower]

I think it doesn't leak.

Edit: But now you have a permanent Rect in your map. I can't see any practical use for that.

 

[Dr Super Good]

It does leak the handle object itself as it has no garbage collector for handle objects. It does not leak a handle reference counter however. This means that if you destroy the rect later in another function it will not leak.

 

[ic3_water]

Since you have removed Rect in 2nd function, it doesnt leak

 

[Adiktuz]

@ic3 = he was asking if the first method will leak, in which case would mean that he needs the second one (which is why he also asked if he needed to do that second method)

basically, he asking either if method 1 is fine, or he needs to use method 2...