The question how to clean this up somewhat depends on fluid_synth_error(). This function returns the global buffer used by fluid_log and is therefore not thread safe. One could try to make it thread safe (perhaps with some fancy macro hack, havent come up with a proper solution though) or deprecate fluid_synth_error(), remove FLUID_LOG and call it directly.
Deprecating fluid_synth_error() should be ok, as the user can register custom logging functions anyway, that allow to use error messages arbitrarily. Tom _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
