No, it's not. Don't do that. Someone (like me) will replace assert.h wholesale and it will not behave the way you expected. Always define your own internal macro and always provide facilities for the user to override it.
> 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