struct _key_fntable_int incompatible with memory leak detectors

[marcstern]

Most memory leak detectors redefine the "free" function (and others).
The struct _key_fntable_int contains the following:
void (*free)(cjose_jwk_t *);
This clashes with a redefintion of "free".
Is it possible to rename this field (like "free_func")?
Thanks

[veselov]

This won't be a problem for normal memory leak detectors, unless they redefine free in the preprocessor stage, which, I imagine, will wreak all kinds of havoc. Leak detectors (i.e. valgrind, are there others that are used actively?) substitutes symbol tables (or doing something of the sort), this will neither affect local symbols nor structures fields (those aren't even exposed as symbols after compilation).
Which memory detector are you having problems with?

[marcstern]

Several memory detectors do indeed define free (and malloc, alloc, ...) to add the filename & line number to the info. One concrete example is the Microsoft one integrated to Visual C++. And I met several others also.
As this change is trivial and cannot break anything, it's a (very) quick win.

[zandbelt]

this is now part of the maintenance fork here:
https://github.com/OpenIDC/cjose/tree/version-0.6.2.x