Are hashtables infinite?

[Mufanza]

Hi
I've created some mighty bad-ass system in my map that cover knockback, missile projectiles and whatnot...
It's all done with units custom values + sheetload of arrays, everything done before hashtables were there for me to use...
Now, I've been wondering about re-writting the code and converting it all from custom values to hashtable values...

...Is it worth it?

-Are hashtables infinite? I know that unit custom value has maximum integer number of something over eight-thousaaaaaaaand
-Are they slower/faster/something?
-Is there something else I should take into account?

Ok thanks for any reply, cheers

 

[PurgeandFire]

- 256 hashtables maximum (shouldn't really need to go past that). I forgot what the exact maximum keys and stored values are, (DioD made a post with the maximums in wc3c, but wc3c is down) but it is something over a billion so it isn't something to worry about.
- They are fast, but not as fast as arrays and custom values. (difference in speed is unnoticeable though)
- If you are likely to get custom values > 8191, then switch to hashes, otherwise custom values will be fine. You can also include optionally which to choose.

Fire away if you have any more questions.

 

[Bribe]

FYI, Hashtables also enable you to have instance-associated-arrays. In my TimeTravel system, I do this:

SaveReal ( hash , this * 3 , savepoint , x ) ;
SaveReal ( hash , this * 3 + 1 , savepoint , y ) ;
SaveReal ( hash , this * 3 + 2 , savepoint , z ) ;

x = LoadReal ( hash, this * 3 , savepoint ) ;
y = LoadReal ( hash, this * 3 + 1 , savepoint ) ;
z = LoadReal ( hash, this * 3 + 2 , savepoint ) ;

This enables my system to have 3 arrays indexed to each instance, causing 'hash' to act as a 3-dimensional array.

 

[Axarion]

The limit for hashtables is nearly unreachable, so its enough to use 1 for your whole map
They are like 60% slower than arrays but quite fast though.

 

[Mufanza]

You can also include optionally which to choose.

What do you mean?

Fire away if you have any more questions.

Thanks man! And thanks for the reply as well

SaveReal ( hash , this * 3 , savepoint , x ) ;
SaveReal ( hash , this * 3 + 1 , savepoint , y ) ;
SaveReal ( hash , this * 3 + 2 , savepoint , z ) ;

Sounds cool... But wait, what does "this" refer to?

They are like 60% slower than arrays but quite fast though.

Aw that sounds like quite a lot
I'm using about hundred of values every 0.02 seconds!

Let me think some more... I don't need custom values for dead units - I'm certainly not going to have more than 8191 units on the map at the same time. So... I could theoretically fix the maximum custom value limit by looping through all living units on the map once the custom value gets past 8190, and change their values while in there.
Would it be faster than using hashtables though? (it shouldn't happen too often though)

 

[Mufanza]

Hold on a minute!

I just tested this:

• Melee Initialization
  • Events
    • Player - Player 1 (Red) skips a cinematic sequence
  • Conditions
  • Actions
    • Set i = 999999
    • Unit - Set the custom value of Footman 0000 <gen> to i
    • Game - Display to (All players) the text: (String((Custom value of Footman 0000 <gen>)))

And it worked!

Could anyone riddle me this? Because my explanation would be something along the lines of: Maximum value in an array is 8191, but it seems to be a lot bigger for casual integer, which is a custom value, for example...

If I'm not mistaken, then it's awesome! and it solves the problem as well it seems...
Or is something fishy behind it?

Including proof map:

 

[Axarion]

big loops are worse than hashtables i think ^^

the other thing: i dont know if custom values have a limit, but arrays have also you can set an array to x[1] = 999999

 

[ikillforeyou]

he means if you have 8191 units with custom values defined, the next one won't store a custom value.

like doing this
set V[8192] = 100
call BJDebugMsg(I2S(V[8192]))

wouldn't even type anything, as it would be referring a null value.

 

[Mufanza]

he means if you have 8191 units with custom values defined, the next one won't store a custom value.

like doing this
set V[8192] = 100
call BJDebugMsg(I2S(V[8192]))

wouldn't even type anything, as it would be referring a null value.

Fcuk!

So if I understand it well, I can have 8191 units, each holding custom value, but it's irrelevant how big the custom value is?

Hmmm

So can I null units custom value somehow?
Each time a creep dies, I don't need to store its value anymore :S

 

[Axarion]

I think it doesnt store it anymore automatically

 

[Mufanza]

I think it doesnt store it anymore automatically

Ah, that comforted me a bit
Still, does anyone know for sure?

 

[chilla_killa]

There are only 2 things that are infinite.
The universe and the stupidity of the human beings.
But I'm not really sure about the universe.

 

[ikillforeyou]

if you remove the unit it clears the value.