If there are config macros to disable the offending macros then that's the solution. I realize it's difficult for Qt and Apple to turn them on by default but this shouldn't be that hard for their users. And perhaps it should be advertised as the recommended way of working with Qt. Eventually, this should become headache for Qt devs and those who use these macros in API, not for us.
qt cannot change their defaults, as it would change their API. boost can address the default *without* breaking the API. the headache is not for Qt devs, they don't use boost. the headache is for their users. just like, it is not your headache or joaquin's, but the headache of their users. lets please try not to be dogmatic about it, that won't lead anywere. instead we should to work towards a robust solution, which solves real-world problems.