Hacker News Reader

> 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.

This is totally backward. It's literally not any standard practice I have ever seen. In fact, it is an anti-practice. If you go around re-#defining standard library macros then you get what you deserve, and get no sympathy from me.

And it seems completely sensible that if I'm writing a C++ library that it's header files should include assert.h, and use assert()'s in its inline functions. And you will get no sympathy from me if you break my code by redefining the library behavior of assert().

So basically you didn't bother to look and then blindly declared it an anti-practice?

What exactly would you like me to look at that I haven't looked at already?

Reply on news.ycombinator.com