Home/ Questions/Q 6740407
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T11:36:08+00:00

I want to generate int from a string and be able to generate it

  • 0

I want to generate int from a string and be able to generate it back.
Something like hash function but two-way function.
I want to use ints as ID in my application, but want to be able to convert it back in case of logging or debugging.

Like:

int id = IDProvider::getHash("NameOfMyObject");

object * a = createObject(id);

...

if(error)
{
    LOG(IDProvider::getOriginalString(a->getId()), "some message");
}

I have heard of slightly modified CRC32 to be fast and 100% reversible, but I can not find it and I am not able to write it by myself.

Any hints what should I use?
Thank you!

edit
I have just founded the source I have the whole CRC32 thing from:

Jason Gregory : Game Engine Architecture

quotation:

“As with any hashing system, collisions are a possibility (i.e., two different strings might end up with the same hash code). However, with a suitable hash function, we can all but guarantee that collisions will not occur for all reasonable input strings we might use in our game. After all, a 32-bit hash chode represents more than four billion possible values. So if our hash function does a good job of distributing strings evently throughout this very large range, we are unlikely to collide. At Naughty Dog, we used a variant of the CRC-32 algorithm to hash our strings, and we didn’t encounter a single collision in over two years of development on Uncharted: Drake’s Fortune.”

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Reducing an arbitrary length string to a fixed size int is mathematically impossible to reverse. See Pidgeonhole principle. There is a near infinite amount of strings, but only 2^32 32 bit integers.

    32 bit hashes(assuming your int is 32 bit) can have collisions very easily. So it’s not a good unique ID either.

    There are hashfunctions which allow you to create a message with a predefined hash, but it most likely won’t be the original message. This is called a pre-image.

    For your problem it looks like the best idea is creating a dictionary that maps integer-ids to strings and back.

    To get the likelyhood of a collision when you hash n strings check out the birthday paradox. The most important property in that context is that collisions become likely once the number of hashed messages approaches the squareroot of the number of available hash values. So with a 32 bit integer collisions become likely if you hash around 65000 strings. But if you’re unlucky it can happen much earlier.

    • 0