... > You must realize that our small team had our hands full just producing > Judy IV (the fourth and final version, massive rewrite, the one put on > SourceForge) before HP cancelled the project. We only scratched the > surface in several directions, such as shipping Judy with it's own "good > malloc()" (but then the linking application must use it too),
The right direction is to remove any malloc library from inside Judy. If you think Judy really needs it and you have idea how to implement it, IMHO it is MUCH better to open SEPARATE project related only to malloc and to keep Judy as small as possible. This way is more flexible. I beleave Judy users know better what kind of malloc should be used. -- Best regards, Aleksey Cheusov. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
