[Trigger] I have two questions.....

[sephiroth1234]

Q1o Hashtable Handles leak? If yes, how to clean them?

Q2: How to save and load independent data(real, integer, unit, destructible, etc.) of units, destructibles, etc. without using a Hashtable? I'm wondering if that can be done only in JASS but is there a way in GUI?

 

[Tirlititi]

A1:Yes, when you init an hashtable, you actually create an handle and if you don't want to use it anymore, you should destroy it. But in fact, you are coding very bad if you use a lot of hashtables in jass and leak is not you first priority. One hashtable is largely enough in most case.

A2:You can use a vJass unit indexer or a game cache like this :

• Game Cache - Store handle as MyHandle of (String((Key (unit)))) in (Last created game cache)

It was used a lot before hashtables appeared but since it's less efficient and slower, it's not used anymore.
If you don't want to use hashtables or game caches, you would have to simulate a vJass unit indexer in GUI which can certainly be done but would be ugly.

 

[Bribe]

GUI Advanced Indexing and Data Storage should work wonders, from what I can tell.

http://www.thehelper.net/forums/showthread.php?t=130752

 

[Bannar]

I gonna give you an example for multuple units about it.
It's form another request, hope you it gonna help you.
Here it is, Fearless Helm map.

Example is about life reg, trigger counts what have to be counted and than restores life. Regeneration changes rapidly since it's based on current life of given unit.

 

[sephiroth1234]

E1: Then that means....

• Hashtable - Save handle of (Picked unit) as Key(Picked unit) of Key(Picked unit) in (Last created hashtable)

This part Key(Picked unit) does not leak?

 

[Odellia]

Yes, just destroy/clear the Hashtable after your done using it.

 

[Bribe]

No, it does not leak at all. Picked Unit does not leak, and Key(Picked Unit) gets the unit's handle id (integer). No leaks.

If you save 2 ^ 32 (an extremely high number) of things in a hashtable, that's when you hit the hashtable's storage limit. The game consumes about 2 GB of RAM at that point XD

Good thing is it would take a LOT of effort even get close to that limit.

 

[sephiroth1234]

I get it! The handle is an integer and integers do not leak am I right?

 

[Deaod]

The handle is an integer and integers do not leak am I right?

Partly: Integers dont leak, yes.
But handles are not integers, handles are a different primitive type. Every handle can be "casted" into an integer, though (which is what GetHandleId() does). Every handle has an ID, which is unique for all subtypes of handle (there are no two units with the same ID that are not the same unit), some even share a stack of IDs (units, groups, timers, and a few more. This means that if a unit has a certain ID, there can be no group with the same ID).

Anyway, if you ever have to destroy a hashtable handle, youre doing something VERY wrong. So dont worry about hashtables leaking.

There are arrays...

 

[sephiroth1234]

Finally, thanks for the time. XD

 

[Bannar]

Oh, i'm sad panda, i tho you want trigger that 'store' (some counting, not the same as in hash) some data without using hash... Sorry for mistake, i gonna read it more carefully next time.