On Thursday 03 January 2002 08:11 am, Chip Turner wrote: > The U was there for sign-correctness. Without it, gcc complains in a > number of places. I haven't tested it on 64-bit platforms, but on > 32-bit intel, it is necessary. > > uintptr_t sounds good to me, though; always using pointers seems > preferable to constantly mixing them at every comparison, anyway.
Some compilers don't allow bit operations on pointers. Hence the There And Back Again conversion to an integer. O course, that introduces its own problems... -- Bryan C. Warnock [EMAIL PROTECTED]
