I'd like to use JudySL for a unique map between zero-terminated strings and a 64-bit pointer. The value, however, is Word_t, defined in Judy.h as only an "unsigned long". (Specifically, I'm using C++, Visual Studio 2010.)
Searching through the mailing list archive, I found this suggestion from John Skaller for how to modify Judy.h so that Word_t will be an "unsigned long long" when compiling for 64-bit systems. http://sourceforge.net/mailarchive/message.php?msg_id=27014844 I have two questions about using it, and one about the performance. 1.) Am I right in thinking that the necessary goodies are simply the lines inside the "#ifndef _WORD_T"? I was hoping it would be that simple. (Though it looks like the rest of John's modifications include tweaks for making it work with Visual Studio, which I would want to use, too.) 2.) Is that really all that's necessary? Are there any additional tweaks that would optimize JudySL for a long long Word_t Value? 3.) Has anyone done benchmarking on the effect of increasing Word_t to a long long? I imagine there would be hardly any speed impact. Thanks! --- Tim Margheim ------------------------------------------------------------------------------ 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
