Hm. My original idea here was that since any function that replaces free() as used by mm_free() is provided by you, you would know what function to call.
That is, if you used event_set_mem_functions() to replace free() with my_free(), then you would just call my_free() on anything allocated by libevent for you. Make sense?
That said, there's no inherent reason we couldn't rename event_mm_free_() to event_mm_free() and expose it in the headers, if there's some reason that it's hard to call the right free() function on returned memory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hm. My original idea here was that since any function that replaces free() as used by mm_free() is provided by you, you would know what function to call.
That is, if you used event_set_mem_functions() to replace free() with my_free(), then you would just call my_free() on anything allocated by libevent for you. Make sense?
That said, there's no inherent reason we couldn't rename event_mm_free_() to event_mm_free() and expose it in the headers, if there's some reason that it's hard to call the right free() function on returned memory.
Closing as not-a-bug; making this point even more clear in the documentation.