Doug, nice explanation.
> (The macro JLI() also allows you to define many error handing methods,
> but to my knowledge, nobody ever uses this powerful feature).
Well, I do! Using the macros for many Judy1/L/SL arrays in production
code, I have a section to #define JUDYERROR in the main header file.
AND, since libJudy calls are made in functions with various return
types, I have JUDYERROR return JUDY, which unfortunately leads to code
like this before the first J*() call in any function:
#undef JUDYRET
#define JUDYRET FALSE // or PP_ERR or NULL or whatever.
JLI(...);
This is potentially a source of latent bugs, but I wrote a Perl script
that checks my C code to ensure I have a JUDYRET defined before the
first J*() call in each function! Wasn't hard.
Alan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Judy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/judy-devel
