> Judy makes the same mistake in the headers. Pvoid_t. Oh, come on, > this is a stupid choice of names and totally unnecessary. The correct > way to spell void* is 'void*'.
Hmm... If it's truly a problem, mea culpa. We were trying for clarity and consistency. I've also run into big old code that used what I thought was "unnecessary" abstraction, which only made it harder to find instances, etc. Like #define'ing GLOBAL to "extern". I don't know that I'm convinced it's so bad to use something like Pvoid_t, though, even if it's unnecessary to the compiler, should never change meanings, etc. So long as it's used consistently, it does add a layer of explanation, "we meant to do this, and this is what we expect it to mean." Then again, taken out of context (not worrying about consistency or affinity with similar typedefs), it does seem kind of silly and I don't know why I might do it today. Perhaps we had what seemed like a good reason? We'd been burned by various portability issues, and tended to err on the side of creating our own consistent abstraction layer to hide the details of getting stuff right on each platform. 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
