Hash tables, do they leak?

[I_H8_U_M8]

Clearly from the title, I would like to know if abstract handlers leak in hash tables as they do in variables? If so, how would you go about freeing them, or is the only way to free them to free the table parent or child itself? Could some one explain what leaks with hash tables, that would be great.

 

[Berb]

Well there are these functions too:

native RemoveSavedInteger
native RemoveSavedBoolean
native RemoveSavedString

In addition to:

native FlushParentHashtable
native FlushChildHashtable

 

[Rui]

I didn't know about the Remove functions. I don't understand, though. How come Booleans, Integers and Strings have to be removed? And if so, what about Reals?

 

[sephiroth1234]

The best way to prevent a Handle, Hashtable or whatsoever to leak is to clear the specific parent of a Hashtable.

 

[Berb]

And if so, what about Reals?

native RemoveSavedReal

 

[I_H8_U_M8]

I mean, well, you know how points are one of the most common leak?
Well, say you saved a point in a hash table, would you have to save the point as a temporary variable like P_Loc then clear the parent it is referenced in, then destroy the point?

    set udg_P_Loc = LoadLocationHandleBJ(0, 0, udg_HT_SomeName)
    call FlushChildHashtableBJ( 0, udg_HT_SomeName )
    call RemoveLocation(udg_P_Loc)

 

[ap0calypse]

As it is still a reference to a handle (location), I would say yes, you do.
And even if you don't, it doesn't hurt to do it anyway.

I wouldn't save locations though, instead I would save coördinates: they're a LOT better.
(faster, no problems like this, easy to use).

Edit: could you next time use [code=jass] [/code] or [trigger] [/trigger]?
(To copy/paste GUI-codes, right-click the trigger name above "events" and select "copy as text").

 

[Berb]

Typically when I use hashtable values (usually the only thing you need to save is an integer, because of how structs are implemented) I just use RemoveSavedInteger to clear the memory references. I rarely use FlushChildHashtable or FlushParentHashtable.

 

[I_H8_U_M8]

kk, thanks then everyone