On 23/10/2012, at 11:27 AM, Doug Baskins wrote: > > P.S. It has been suggested that the 4 JudyxTables.c files be delivered, > rather than constructed. > I give them the names: JudyLTables32.c, JudyLTables64.c, Judy1Tables32.c and > Judy1Tables64.c > in the new Judy. But I still use the JudyTables.c tool to construct them.
This is a good idea. I would also suggest that those JudyL/Judy1 codes generated by the same file with command line macros be replaced by *.include file and two C files which include them with the macros set in those files. It should be possible to build Judy by simply compiling all the *.c files in the library directory and linking them to a DLL or making a static link library. I would personally recommend going to C++ and eliminating as many macros as possible. C++ allows better factorisation of common code, including with routine polymorphic over the word size. Some conditional compilation may still be needed. As a matter of interest, has Judy performance on ARM processors been considered? [I know it builds on iOS] Also, have you considered a public repository for your work so you can get help and feedback from the small user community? -- john skaller [email protected] http://felix-lang.org ------------------------------------------------------------------------------ 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
