> (one method to help find violations between old 32 bit values and new > 64 bit values is to make the 64 bit value a pointer, which triggers > conversion to different size warnings, and eg, display needs a > PRIx<PageCountType>, etc., set, as well as other things likely to > come up. it seems worth paying the price given the almost impossible > task of finding all the conversions by hand.)
Or make the new value a struct containing the actual value - you don't need casts, you aren't using a conceptually wrong type, and the resulting code is in most cases just as small and fast as using the undecorated 64-bit type. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
