hash_32bit
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | hash_32bit [2007/03/02 02:32] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # $EPIC: hash_32bit.txt, | ||
| + | ======Synopsis: | ||
| + | $__hash_32bit__(< | ||
| + | |||
| + | ======Technical: | ||
| + | * The < | ||
| + | * If the < | ||
| + | * If the < | ||
| + | * If the < | ||
| + | * The return value of this function is a 32 bit signed integer that is a " | ||
| + | * Analytically speaking, hashing is a specific type of lossy compression. | ||
| + | * All lossy compression techniques suffer from " | ||
| + | * The inverse of this principle is that all lossy compression techniques are irreversible. | ||
| + | * The return value of this function is deterministic within the lifetime of the client. | ||
| + | |||
| + | ======Practical: | ||
| + | You can use $__hash_32bit__() to convert an arbitrary string (perhaps | ||
| + | containing characters that cannot be used in alias names) into a 32 bit signed | ||
| + | integer value which you can use as part of an alias name. Collisions will | ||
| + | occur. | ||
| + | function. | ||
| + | |||
| + | ======Returns: | ||
| + | A 32 bit signed integer (it can be either negative or positive) that | ||
| + | is deterministically derived from the first < | ||
| + | |||
| + | ======Examples: | ||
| + | $hash_32bit(" | ||
hash_32bit.txt · Last modified: 2007/03/02 02:32 by 127.0.0.1
