alt Hacker News> Always define your own internal macro and always provide facilities for the user to override it.
that kinda sounds even more insane and cumbersome
> Always define your own internal macro and always provide facilities for the user to override it.
that kinda sounds even more insane and cumbersome
It's literally standard practice. You import assert.h unless the end user has defined mylib_assert in which case you don't import and use that instead. Failing to do this can result in all kinds of dumb problems thanks to the namespace being global.