Tim et al, > I'm working on Win64 (LLP64 model), not UNIX (LP64 model).
Gotcha. I don't recall hearing those terms before, maybe years ago and I forgot. I found this 15-year-old explanation: http://www.unix.org/version2/whatsnew/lp64_wp.html > In Win64, an unsigned long is /always/ 32-bits, but in UNIX it scales: > 64-bit in a 64-bit compile. In order to get a 64-bit int, I need to > define it as "long long" or "int64". I see. I wasn't aware of this (portability) difference between the two OS types. Sigh, more "Tower of Babel Syndrome." I guess that's why "they" recommend using types.h aliases instead of base types like int and long. And I guess we didn't do that in libJudy header files? Odd, I know we compiled it for 32+64 on both HPUX, Linux, and WinXP. > It's good to confirm that Judy *was* written to work with a 64-bit > Word_t. Oh, absolutely. > I shouldn't have anything to worry about, once I add the conditional > type declarations. At that point they should be equivalent. Don't > you think? Yeah, I think that's true, just surprised any post-facto fix is even needed, seems like #ifdef's in the Judy header files would already have handled it (unless we overlooked something).. Cheers, Alan Silverstein ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
