> Ok, sorry .. found the bug. Set uses void** but others use void*. Yeah, undeniably the asymmetries at the function level have confused people over time. That's why Doug created the macro layer. I believe the signatures are "correct" in a philosophical sense, but since care must be taken to use them properly, it IS an obstacle to using the library successfully.
Hey, does the use of PPvoid_t and Pvoid_t for clarity help prevent problems, through compile-time warnings? Or are compilers "helpful enough" that they figure void ** = void * and they don't tell you? I know we debated on whether the library API should be at a higher level, such as the user passes in the value to JudyLIns(), etc. We decided that would get in the way of the experienced user, and possibly damage performance, more than provide value. Alan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
