Re: PHP3 and 64-bit land

> > Resources use hash tables to store themselves, and they usually use the > > numeric indices. I think it's extremely safe to use 32-bit integers as > > unique identifiers for 64-bit pointers, by simply casting them. You'd > > have to be extremely unlucky to bump into a problem because of this data > > loss. Your chances of winning the lottery are much much bigger. > > I disagree here. The chance of having the same ptr in 32 bit is about 1 in > 2^32 = 4,294,967,296. If you come to Germany, your chance to win the lottery > ("6 aus 49") is about 1 to 49!/43! = 10,068,347,520. > > It's extremly safe, but you risk random, non repeatable crashes produced by > playing that way. Would there be a big drawback to using a long here instead of an int for unique identifiers? -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net