Compatibility syntax

[marcstern]

Visual C++, in debug mode, redefines alloc functions (to detect memory leaks).
The syntax used in this project is incompatible with the redefinition.
Would it be possible to prefix the functions with 'yajl_' in the yajl_alloc_funcs struct?
Thus yajl_malloc(), yajl_free, yajl_realloc.
It's trivial but it makes a huge difference when you need to compile with Visual C++.
Thanks

[robohack]

Do you mean change the names of the members of yajl_alloc_funcs?

That would be an API change, so no that's not possible without a major version bump.

Sounds to me like the machinations of Visual C++ are incompatible with C syntax.

[marcstern]

I understand.
Maybe a #ifdef switch to allow the other syntax?

[robohack]

So I'm still struggling to understand the true nature of this problem with Visual C++.

Is it somehow mangling all symbols matching malloc, realloc, and free, even if those symbols are not representing function calls? How is it implemented, a simple #define set, or something even less safe?

I don't want to break the API compatibility just for Visual C++, but I also don't want to force an API change for everyone just to work around Visual C++ brain damage. Struct member names are supposed to be in a separate namespace from function names.

[marcstern]

Visual C++ uses #define which, unfortunately, also redefines struct members.
Having an #ifdef to choose the struct members names would be an opt-in, so no changes unless requested.