At present the judy1/L modules have quite a bit of code which
is first shared then specialised (threaded).
The Makefile copies the common code from JudyCommon to
Judy1 or JudyL, giving the new file a new filename corresponding
to the target, then compiles those files with macros to select
whether it's Judy1 or JudyL.
Why not just provide files like:
// JudyL/JudyLNext.c
#define JUDYL
#include "JudyNext.c"
This (a) avoids copying, (b) sets the macros, avoiding
needing to put them on the compiler command line
(which may not port to eg MSVC++)
Instead you'd need -I{DEVBASE}/src/JudyCommon on the
command line .. but that's needed anyhow for the shared
private headers.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
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
