On 04/02/2011, at 4:32 AM, Alan Silverstein wrote: > >> 5. Fix the disgusting build system. > > Yeah, for that I apologize myself, it was the best I knew how to do at > the time with the tools in hand. Linux autoconf/etc weren't well known > to us.
Gak, they're even more disgusting! :) Judy needs very little configuration data: 32 or 64 bit and a typename for "Word_t" = uintptr_t is about it. However a lot of stuff is done to avoid duplication by generating various information. In Felix version of the code base, I just generated the only two sane options (32, 64 bit) and the choose between them. Nothing wrong with generating tables, but it should be necessary for the building of Judy, since that involves compiling and running code on the target platform which doesn't do well if you're cross compiling. Anyhow I think a small team can easily fix this stuff without changing any of the actual code. BTW: Felix uses Python script to build Judy. We won't touch make, let alone autoconf. We need code that builds on Windows too. >> My basic opinion is: Judy is very well designed. but it isn't well >> known or used as often as it should be. > > Yeah, that's about right I think. I've always been disappointed that > something so profoundly significant we discovered turned out to be so > hard to embody, explain, share, and put into use. So it goes. Ah well .. Felix is becoming the best programming language around but has no users apart from me :) So it goes.. -- john skaller [email protected] ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
