What's going to happen with Judy? Is there any interest doing some development on GitHub? [Felix project already has Judy on GitHub]
What I'd like to see, initially: 1. Get rid of the confusing macros. Nice idea, but the confusion between lvalues and values is made worse with the macros. More precisely, keep the macros but move them to a separate file. 2. Fix the documentation to provide more detailed explanation of each function. At present you have to understand the conventions and mentally figure out what should be happening. 3. Provide a lightweight C++ wrapper. 4. Think about re-entrant version of the Google version, which reduces the overhead in JudyNext having to lookup the key it found last time. The google version stores the internal state so the next call can proceed without a full scale lookup from the top. However it does it the wrong way, embedding the state in the array, instead of making the client hold it. 5. Fix the disgusting build system. 6. Make it possible to build BOTH 32 and 64 bit versions on all platforms. It's not clear 32->64 and 64->32 bit JudyL can be done, but is there a reason I can't have a 32 bit version on a 64 bit machine? The 32 bit version does 4 level lookups .. the 64 bit one does 8, if my key is an "int" it is only 32 bits anyhow, so the first 4 bytes of the key will always be zero. My basic opinion is: Judy is very well designed. but it isn't well known or used as often as it should be. -- john skaller [email protected] ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
