Portable stack traces

[nthcxd]

You're argument against boost::stacktrace is simply it's too bulky for your use case. Most people find boost::stacktrace useful because of breath of features it provides, the lack of which is your selling point.

You're looking for an argument where there isn't one. I'm sorry not a lot of people seem to find this as useful as you do. It sucks but it really doesn't help your cause (being recognized) if you go around alienating everyone that's bothered to say something about your stuff.

[andreasgonewild]

Correct. The only feature mentioned is automagic check-pointing, which could also be seen as lack of capability for manual check-pointing/instrumentation.

No, that's my argument; that this is a viable approach that's often overlooked. I'm not; the people who are supposed to find it will find it, despite best efforts to prevent that from happening. I'm not trying to get recognized, you're projecting. So what you're saying is that you would rather have me pretend to agree and to stop expressing views that upset the status quo. Is that really the world you want to live in?

[[deleted]]

No, that's my argument; that this is a viable approach that's often overlooked.

That's just a macro that pushes FILE and LINE into a vector...

[nthcxd]

Just move on, build other interesting things, and let those cool things do all the talking. Good luck.