1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. One of WC3's biggest patches is live: 24 player maps, editor updates, widescreen, and more! All the information is here.
    Dismiss Notice
  3. The Cinematic Contest #7 poll is up!
    Dismiss Notice
  4. The Terraining Mini Contest Reload #2 - Machinery has begun! Create a scene centered around a piece of machinery. Get creative tinker boys and girls!
    Dismiss Notice
  5. The Cinematic Contest #7 - Time has begun! Create a cinematic about Time!
    Dismiss Notice
  6. The Concept Art Competition #11 - The Youngest (or) Oldest Warrior has begun! Create a unique warrior concept-art. Get wild with your ideas!
    Dismiss Notice
Last Activity:
Apr 17, 2018 at 10:20 AM
Jul 30, 2013

Following 1


Dedicated Survivor n' dev

Waffle was last seen:
Apr 17, 2018 at 10:20 AM
    1. Ezekiel12
      Hey, you wrote this:

      "eg the following could in rare cases be true and cause heisenbugs:
      StringHash(a) == StringHash(b) && StringHash(a) != StringHash(b)"

      Which edge cases do you mean?
      1. View previous comments...
      2. Waffle
        ... (split cuz 1k char limit..)

        this is the type of silent and rare type of data corruption that is very hard to detect .. also its ocurring conditions are verr particular/situational because they are dependent on data that changes form game to game.

        also you should know that there are way more possible strings than there are 32 bit integers thus there must be many strings whose hashes are the same. but since most maps use very few string it is very rare and thus the issue gets little press. thus not getting fixed and always putting everyone at risk without them realising it.
        Feb 25, 2018
      3. Ezekiel12
        I see what you mean, your posted code still can never be true.

        The problem you are describing all starts with hashtable taking integer as key, therefore the StringHash function has to return an integer.
        This is probably for performance reasons and to emulate the way gamecache was used in combination with the return bug until 2009. When that was found being able to virus other peoples PCs, hashtable and GetHandleId(...) was introduced.
        Feb 25, 2018
      4. Waffle
        Precicely. in normal programming languages the key to a hashtable is the key object itself, but in jass it is instead an integer derived from the key object not the key object itself. (ofc hashtables all use integral hashes underneath the hood but having the actual key object as input allows for dealing with hash collisions transparently, since w3 hashtables do not store the key itself they are unable to deal with .. or even detect that such an issue has occurred)
        Feb 26, 2018
    2. BlueSaint
  • Loading...
  • Loading...
  • About

    Home Page:
    Current Project:
    Fortress Survival Alpha
    WarCraft 3 Account:
    WarCraft 3 Realm:
    US East


  • Loading...